* For the first few days, please get approval from the current
sheriff before pushing anything into mozilla-central, so that we can
make sure that our infrastructure will scale and that there aren't any
unforeseen problems with the hg setup.
* The tinderbox is currently at http://tinderbox.mozilla.org/Mozilla2.
After Firefox 3 ships we'll do some renaming and rearranging, but we
didn't want to make those changes until Firefox 3 was done.
* MXR for mozilla central is at http://mxr.mozilla.org/mozilla-central/
* hgweb is at http://hg.mozilla.org/mozilla-central/; at the
moment, this should be considered a replacement for bonsai, which is
no longer available.
* The tinderbox is missing the 'guilty' column; this will be fixed
in bug 419949. Each build will identify what changeset it's built
from in the tinderbox waterfall though, so that information is still
available.
* Nightly builds are identifying themselves as 3.1a1pre, and are
available in the usual location at http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
* Some mozilla-focused documentation on Mercurial is at on MDC —
specifically, you should read Mercurial Basics and probably the
Mercurial FAQ, both linked from http://developer.mozilla.org/en/docs/Mercurial.
* For pushing to mozilla-central, you'll need to use the ssh
protocol (ssh://hg.mozilla.com/mozilla-central). If you have problems
pushing/pulling use ssh, you'll likely need to file a bug for IT to
fix your committer account permissions.
For Firefox, XULRunner, and anything they depend on, CVS trunk should
now be treated as the Gecko 1.9.0.* / Firefox 3.0.* branch. Like the
practice for previous stable branches, requests for approval to land
on this branch should be for patches that have already landed on
mozilla-central. mozilla-central is the main integration point (as
CVS trunk was in the past) for all changes intended to be in future
Firefox, XULRunner, and Gecko releases. This means that bugs should
be filed against "Trunk"; any bugs in Firefox 3/1.9.0 should be filed
against the "3.0 Branch" or the "1.9.0 Branch" in Bugzilla.
Development of other projects, such as Thunderbird, Calendar, and
SeaMonkey, will follow the rules established by those projects. This
announcement does not cover them. The current plan is that the
mozilla-central repository is for only for Firefox, XULRunner, and the
Gecko/Toolkit code that they depend on; other projects may migrate to
mercurial, but if they do so, the project-specific code will be in a
separate repository.
All changes landed in CVS up through build 2 of Firefox 3.0 RC 2 have
been merged into mozilla-central. The last merged change is:
15200:9a2801dccb5d dtownsend -- Backout of bug 357670 due to bug
434914. a=shaver
Fri May 30 07:32:43 2008 -0700
Any changes made in CVS after this change will NOT be merged into
mozilla-central.
We also plan to be stricter about regressions on mozilla-central then
we have been in the past, as we always want mozilla-central to be as
close to shippable as possible. Commits that cause serious
regressions should be reverted until they can be relanded with the
regressions fixed. As commits are tracked individually in hg, it may
be tempting to push a group of commits all at once. Please refrain
from doing so, as it makes tracking down regressions much more
difficult! If a group of commits causes a regression, the entire
group will be reverted. Please take advantage of the
http://wiki.mozilla.org/Build:TryServer to test out patches before
landing!
Please report any infrastructure quirks or bugs in the
mozilla.org:Release Engineering component in Bugzilla. If you have
problems with mercurial, please drop in to #hg on mozilla IRC; a bunch
of people will be around that can help you out. Happy hacking!
Is there a bug to track a simple way to get all the checkins that happened
between two given builds? And a simple way to get all the checkins that
happened between two given dates? Ideally this would let someone do some
regression-sleuthing without needing an actual trunk pull...
vlad pointed me to
<http://developer.mozilla.org/en/docs/Mercurial/Desired_Features>, which looks
like it might cover this.
-Boris
-Olli
We've now relaxed this rule, and the tree is open for landings
without metering. (When it's open, that is. I'm told it needs to
close for maintainance shortly.)
One warning, though. The "guilty" column on tinderbox doesn't
currently work. This means that the self-metering that used to
happen by people looking at the guilty column and saying "wow,
there's a lot going in right now, maybe I should wait" has to happen
by people going to look at the pushlog at
view-source:http://hg.mozilla.org/mozilla-central/index.cgi/pushlog
or hgweb at http://hg.mozilla.org/mozilla-central/ .
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
Can we add a link here from tinderbox?
Also, is there a bug on having the hgweb logs auto-linkify "bug NNNNN"?
-Boris
There already is one (and has been since well before mozilla-central
was open). The link text is "hgweb".
> Also, is there a bug on having the hgweb logs auto-linkify "bug NNNNN"?
Not sure; I'd already stuck that on my personal wishlist at
http://wiki.mozilla.org/User:Dbaron/Mercurial_Issues though.
Yes: https://bugzilla.mozilla.org/show_bug.cgi?id=394669
" Make bug numbers clickable for hg.mozilla.org "
As a workaround, Zbigniew Braniecki has published a greasemonkey
userscript that adds links for "bug NNNNN" and "b=NNNNN". It's on his blog:
http://diary.braniecki.net/2008/06/05/hgmozillaorg-linkify-bookmarklet/
~Daniel