Now that mozilla-central has created a mozilla-1.9.1 release branch, we’re updating the comm-central build system to build mozilla-1.9.1 by default.
Here’s a little Q and A that I hope should answer most questions.
Q. Why are we doing this?
A. The next versions of Thunderbird and SeaMonkey will be shipped from Gecko 1.9.1 (which Firefox 3.1 will be shipped from), we need to modify our build system to move everyone onto the Gecko 1.9.1 branch (mozilla-1.9.1).
Q. Why is comm-central not branching?
A. The work and time remaining for Thunderbird 3, SeaMonkey 2 and Sunbird/Lightning is significant enough that we consider branching at this stage to be too early. We will be branching closer to the release. This will save some management of two individual branches.
Q. What happens to current build my repositories?
A. We will be updating client.py. Once you pick up that update, the next time you run client.py it will:
- Move your existing mozilla/ directory to .mozilla-trunk
- It will clone a new mozilla/ directory from .mozilla-trunk (so that you don’t need to download all of the mozilla-1.9.1 repository)
- It will then make your new mozilla/ directory pull from the mozilla-1.9.1 release branch.
Q. What happens to building with mozilla-central trunk?
A. At the moment maintaining comm-central with mozilla-central trunk builds is very low priority. To start with, there will be no comm-central with mozilla-central tinderbox coverage.
We’d like to keep up with current developments so that we don’t stray too far, however the priority is for us to ship the next versions of Thunderbird/SeaMonkey from the mozilla-1.9.1 branch.
We’ll be posting more on how we’re going to manage mozilla-central trunk builds soon.
Q. I want to stick with mozilla-central trunk, how do I do this?
A. If you’re pulling a new mozilla/ tree then you can do:
python client.py checkout –mozilla-repo=http://hg.mozilla.org/mozilla-central/
Otherwise, you can manually pull mozilla-central or mozilla-1.9.1 into the mozilla/ directory.
We’ll be adding additional command-line options later.
Q. What happens to locally-cloned mozilla-central repositories?
A. These will still pull from their original locations. You’ll probably want to update their current pull locations and/or check they are pulling the correct code.