10 releases in 9 days

Between Wed (8th) and Fri (17th), RelEng did ten complete releases. In a few cases, at the last minute the release was not shipped to end users because of another release starting immediately, but all the work had been done already.

While doing all these releases, RelEng also set several new speed records – Firefox releases in 8-9 hours, Fennec releases in ~5 1/2 hours. Nice work. Calmly done. Great to watch in action.

Firefox5.0beta5
go to build: 08jun 14:07
all done: 09jun 15:39
end-to-end time: 25h 32m
RelEng time: 9h 01m

Fennec5.0beta5:
go to build: 08jun 14:15
all done: 09jun ???
end-to-end time: ???
RelEng time: 16h 05m (or 05h 10m – depending on whether you include the time waiting for person to wake up to start this non-chemspill release)

Firefox5.0beta6
go to build: 13jun 15:48
all done: 14jun 17:16
end-to-end time: 25h 28m
RelEng time: 8h 48m

Fennec5.0beta6:
go to build: 13jun 15:48
all done: 14jun 18:11 (stopped because of upcoming Fennec5.0b7).
end-to-end time: 26h 23m
RelEng time: 8h 12m

Firefox5.0beta7:
go to build: 14jun 16:34
all done: 15jun 19:10
end-to-end time: 26h 36m
RelEng time: 9h 08m

Fennec5.0beta7
go to build: 14jun 16:35
all done: 15jun 10:42
end-to-end time: 18h 07m
RelEng time: 5h 24m

Firefox5.0 rc:
go to build: 15jun 14:34
all done: in progress
end-to-end time: in progress
RelEng time: 14h 50m

Fennec5.0 rc
go to build: 14jun 16:35
all done: in progress
end-to-end time: in progress
RelEng time: 5h 24m

Firefox3.6.18build1
go to build: 10jun 20:18
all done: 14jun 17:08 (stopped because of upcoming FF3.6.18build2)
end-to-end time: 3d 20h 50m
RelEng time: 2d 13h 29m (or 7h 22m – depending on whether you include the time waiting for person to wake up to start this non-chemspill release)

Firefox3.6.18build2
go to build: 14jun 17:08
all done: in progress
end-to-end time: in progress
RelEng time: 10h 23m

7 thoughts on “10 releases in 9 days

  1. This is impressive work! Keep it up.

    I would love to see posts about infrastructure and release process changes/scripts you had to make to speed up releases, what you learnt during the 4 to 5 switch and how that will affect further releases.

  2. @Nikhil if you look at https://bugzilla.mozilla.org/show_bug.cgi?id=hg-automation you can see a bunch of bugs that got resolved since the beginning of the year.

    The improvements weren’t specific to the Firefox 4 to Firefox 5 switch but the many many quarters of improvements.

    The latest improvements that helped us the most were email notification at different stages during the release and auto-signing.

    It was awesome to go home knowing that the automation will keep everyone in the loop and that if everything went well required no human interaction after triggering the release 🙂