latest-comm-central -> latest-comm-1.9.1
latest-trunk -> latest-comm-central
plus the same for -l10n, and also a latest-mozilla1.8 for Sm 1.1.x
"Either comm-central or trunk, but not both taken together, ultimately redirect to 1.9.1". Not very obvious.
I suppose the next step will be to add a "1.9.1 Branch" to SeMonkey on Bugzilla — or will it be enough to rename the existing "1.9.0 Branch"? Or should there be a "SeaMonkey 2.0 Branch" as distinct from "Trunk"? Now that the code is forked, I suppose bugs should be reported distinctly, since it isn't always obvious that a "new bug" is in Core (which is forked) or in SeaMonkey-specific code (which, IIUC, isn't).