mozilla-central, mozilla-1.9.2 nightly builds (ATTN: nightly users)

August 14th, 2009

Because of the major version bump in mozilla-central, all users of mozilla-central nightlies will be bumped to mozilla-1.9.2 nightlies today. If you want to continue to track the Firefox 3.6 / Gecko 1.9.2 builds no action is required. If you want to track the post-1.9.2 version or absolute “trunk” of Firefox/Gecko you will need to download today’s mozilla-central nightly build, found in the nightly area of the ftp server.

Posted by bhearsum Filed in firefox, nightly, planet, updates
4 Comments »

4 Responses to “mozilla-central, mozilla-1.9.2 nightly builds (ATTN: nightly users)”

  1. WildcatRay Says:
    August 14th, 2009 at 9:54 am

    Because this was done this way, we now have Branch/Namoroka in C:\Program Folders\Minefield. This now forces us to have to straight this out by download BOTH the new Minefield and Branch/Namoroka builds. What a cluster****!

    What seems more logical to me is that Trunk/Minefield stay that and anyone wanting Branch/Namoroka download and install/unzip it. But hey! That’s just silly old me. What the hell do I know?

    Perhaps in the future you will remember this and handle things better.

  2. Kurt (supernova_00) Says:
    August 14th, 2009 at 12:45 pm

    I concur. What the heck, I downloaded trunk nightlys because I want those. I should be automatically switched to branch because of a version bump. I think this had happened once before but it hasn’t been often so why was it done this time?

  3. bhearsum Says:
    August 14th, 2009 at 12:54 pm

    This happened when we branched for 1.9.1, too. We didn’t have this issue for 3.0 because it was the last version number for CVS trunk. Our update system tracks products by version number, not source repository, which is why this happens.

    I agree that this behaviour is not necessarily intuitive. It is arguably the correct thing, though. Users are staying on the same branch, it’s just being built out of somewhere else.

    It would be great if we could distinguish between “users that downloaded a nightly to use the next version of Firefox early” and “users that downloaded a nightly to stay on the bleeding edge forever”. I think it’s right to default to putting users on the next shipping branch. Anyone who wants to stay on the true bleeding edge may do so. Of course the best case solution here would be to offer users an option when we branch, but that’s not possible with the current server side code nor the front-end updater code.

  4. g Says:
    August 14th, 2009 at 1:07 pm

    thanks for the tip!

Leave a Reply