This covers reports in the areas of Project and Release Management, Community/User Relations, Marketing/Press/PR and web pages within the SeaMonkey project. If you're not sure if what you want to report is specifically about the SeaMonkey project, you should probably consider to use the "mozilla.org" or "website" products for reporting your problem.

As a reference for those following the process, could you provide a brief summary which SeaMonkey branch/version is supposed to end up where?
With mozilla-central going to Gecko 7.0 soon, comm-central/mozilla-central will become SM 2.3, I'd assume. SM 2.2 is moving to comm-aurora/mozilla-aurora, thus staying on Gecko 6.0?
What is the target for SeaMonkey 2.1.x? Staying on comm-2.0/mozilla-2.0 would require a Gecko 2.0.2 release, which may not happen, or is SM 2.1.1pre moving to either comm-2.0/mozilla-miramar or comm-2.0/mozilla-beta on Gecko 5.0?
Sorry if this has been explained somewhere already and I've missed the memo.

(In reply to comment #1)
> With mozilla-central going to Gecko 7.0 soon, comm-central/mozilla-central
> will become SM 2.3, I'd assume. SM 2.2 is moving to
> comm-aurora/mozilla-aurora, thus staying on Gecko 6.0?
AFAIK (Callek is the authority here, but I think I still know this somewhat), Gecko 7 is to be SeaMonkey 2.4 and 6 is 2.3, as 2.2 is planned to come very fast off the Gecko 5 release.
> What is the target for SeaMonkey 2.1.x? Staying on comm-2.0/mozilla-2.0
> would require a Gecko 2.0.2 release
No additional 2.1.x are planned after 2.1 final, which doesn't need any 2.0.2 release but will come off 2.0.1 once the last glitches experienced in the RCs are fixed. The next version is to be 2.2, which will come with very little SeaMonkey-specific work off Gecko 5 just to have a current security release, 2.3 off 6 will probably be similar.

(In reply to comment #3)
> Thanks, I was under the assumption that 2.2 can no longer come from rv:5.0
> as it "missed the train" for the respective aurora/beta deadlines.
There haven't really been any comm-aurora/beta "deadlines" yet as nobody has been using those repos, we're only at the stage of getting them into action right now (with this bug being a major part of that).
And we don't need any changes on the mozilla-aurora/beta side to build releases based on the code currently there. ;-)