Closed Bug 904124 Opened 11 years ago Closed 11 years ago

MozillaBuild 1.8 tracking thread

Categories

(Firefox Build System :: MozillaBuild, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: RyanVM, Unassigned)

References

Details

Tracking bug for Mozillabuild 1.8.

Changes since version 1.7:
* Updated Mercurial to version 2.6.1 (no bug)
* Updated Python to version 2.7.5 (bug 871817)
* Updated yasm to version 1.2.0 (bug 791513)
* Updated emacs to version 24.3 (bug 791512)
* Added support for Visual Studio 2013 and Win SDK 8.1 (bug 889721)

Trial build available for testing here:
http://people.mozilla.org/~rvandermeulen/MozillaBuildSetup1.8.0pre.exe
> Changes since version 1.7:
> * Updated Mercurial to version 2.6.1 (no bug)

From the 2.6.x series, 2.6.3 is out: http://mercurial.selenic.com/wiki/WhatsNew#Mercurial_2.6.3_.282013-07-01.29

Else, 2.7 is also out: http://mercurial.selenic.com/wiki/WhatsNew#Mercurial_2.7_.282013-08-01.29
2.6.2 and 2.6.3 didn't look like they offered anything interesting relevant to how we use it.

And I wasn't comfortable with using a .0 release, even though 2.7 does look like it has some nice fixes.
I agree with you on not using a .0 release. However, 2.6.2 and 2.6.3 contain some bug fixes and are low risk. I vote for going with 2.6.3. If this release drags on for a few more weeks, we should evaluate 2.7.x for regressions, new releases, etc.
I'm hoping to release this week if possible. I don't feel that strongly about a later 2.6 version, so I'll use that if others do.

FWIW, I'm shooting for roughly a quarterly update cycle going forward, so we shouldn't ever be lagging too horribly.
Blocks: 910637
Depends on: 910703
Released \m/
https://groups.google.com/forum/#!topic/mozilla.dev.platform/_9U6160_oyA
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Firefox Build System
You need to log in before you can comment on or make changes to this bug.