TB 3.1 branch plans

Justin Wood (Callek) callek at gmail.com
Thu Apr 15 18:53:37 UTC 2010

This plan sounds good on my end, one question though.

Do we plan to drop 1.9.2 ifdef's globally once branching is done, just 
on build-config (to make mail/ merge's easier) or what?

If the plan is so soon, I can start writing the patch asap to do it (for 
branch c-c and trunk c-c code)

~Justin Wood (Callek)

On 4/15/2010 8:30 AM, Mark Banner wrote:
>  As you all know, at some stage we need to branch comm-central into 
> comm-1.9.2 which is where we'll be releasing Thunderbird 3.1 final from.
> As 3.1b2 is feature/string/code freeze, I'm proposing that we branch 
> after the freeze, but before we start the builds for 3.1b2.
> This means we can get everything in place during the "quiet" period 
> after freeze, and then once we've built 3.1b2 we know that we have 
> pretty much everything in the correct place for the RC builds for 
> final and the 3.1.x security releases.
> The current plan goes roughly like this:
> - Freeze for 3.1b2
> - Start getting infrastructure in place, e.g. create comm-1.9.2 
> repository, set up mxr, etc...
> - On Monday before the builds start, switch over to using comm-1.9.2 
> for 3.1 builds (builders, tinderboxes etc). We may do this step 
> earlier, if everything is in place, and we're not expecting any late 
> checkins for 3.1b2.
> - Do 3.1b2 builds from comm-1.9.2 on Tuesday.
> Note that between the time comm-1.9.2 is created, and an announcement 
> that we've completed the split, please don't push to comm-1.9.2 - this 
> is because we'll be pushing any changes in comm-central across to 
> comm-1.9.2 by hand before we branch development.

More information about the tb-planning mailing list