comm-central has branched

[Mark Banner]

We’ve now branched comm-central [1]. There are now two repositories for
the comm-central applications:

* comm-central [2]: The trunk repository containing source code for
Thunderbird 3.next, SeaMonkey 2.next and Lightning 1.next.
* comm-1.9.1 [3]: The stable branch repository, based on Gecko
1.9.1, for Thunderbird 3, SeaMonkey 2, Lightning 1.0.

If you already have comm-central checked out with mozilla-1.9.1 (the
default until now), you will be automatically switched to
mozilla-central. The mozilla-1.9.1 repository will be archived in your
directory as ‘.mozilla-1.9.1′.

Local clones of mozilla will not be affected, only the ones that point
to http://hg.mozilla.org/releases/mozilla-1.9.1/.

The tree rules [4] page has been updated with the current status and
requirements for checkins, please check that before checking in. The
various tinderbox pages have also been updated.

Whilst we’ve branched, there are still a couple of issues that we’re
resolving on buildbot and some of the builders, so the comm-central and
comm-1.9.1 trees will be staying *closed* until tomorrow morning when
we’ll have hopefully resolved the issues.

Also, comm-1.9.1 isn’t on mxr yet, we have a bug [5] filed to get it added.

Standard8

[1] https://developer.mozilla.org/en/comm-central
[2] http://hg.mozilla.org/comm-central/
[3] http://hg.mozilla.org/releases/comm-1.9.1/
[4] https://wiki.mozilla.org/Tree_Rules/comm-central
[5] https://bugzilla.mozilla.org/show_bug.cgi?id=522681

[Mark Banner]

On 22/10/2009 22:17, Mark Banner wrote:
> We’ve now branched comm-central [1]. There are now two repositories for
> the comm-central applications:

I forgot a couple of things:

- Known issues for comm-central + mozilla-central builds have been
tracked on https://bugzilla.mozilla.org/show_bug.cgi?id=470184

New known issues should just be filed as normal bugs, we don't need to
mark them blocking that bug now that we have branched.

- For Thunderbird related bugs, we're currently discussing the strategy
for flags post-branching.

For now, when you check a bug into comm-central, please mark its
milestone as "Thunderbird 3.1a1pre", if it subsequently gets checked
into comm-1.9.1 then change the milestone to "Thunderbird 3.0rc1".

Once we've sorted out the flags, I'll post more on what to do (and sort
out the bugs as necessary).

Standard8