Last week, we offered Firefox 2 (yes 2!) users a Major Update offer to Firefox 3.0.15. This was despite our official End Of Life for Firefox 2 way back in December 2008.
While most attention is naturally focused on new releases, and on new security releases, there were 5.3% of our users still using Firefox 2. Those users were not getting new fixes and features; even worse, these users were all using versions of the browser that had known, published, exploits – exploits that were already fixed in later supported releases of Firefox.
The previous major update offer was intentionally left available, so any FF2 user who did manual CheckForUpdates would get upgraded to FF3.0.6. However, few did. As most of these Firefox2 users were on FF188.8.131.52, they were obviously willing and able to upgrade when security releases prompted them to. It seemed worth the effort to prompt them again, with a new Major Update offer, and see how many would upgrade.
In the first 7 days after publishing those new major update snippets, 16% of FF2 users have upgraded. Its a slower rate of upgrading then we get for normal security releases. However, its still a significant amount, and its great to see those users get back onto supported, more secure, releases. I’ll continue to monitor uptake, and keep you posted.
(ps: It was really cool that nthomas and abillings were able to find the time to squeeze yet another release into the schedule in the midst of all the releases for FF3.0, FF3.5, FF3.6 beta/RCs and Fennec beta/RCs. To keep this work quick and safe, we did a FF2->FF3.0 MU offer, rather then attempting FF2.0->FF3.5, which would require a bigger testing cycle, details in . On behalf of those users who are only now discovering the Awesome Bar, our faster performance and all the new JIT work, I thank you both!!)
“It was the day my grandmother exploded.”
A great opening line, and it made me stop my browsing in the bookshop to read on, a little curious. By the end of the first chapter, I was hooked and needed to buy the book. This coming-of-age story in rural Scotland is interwoven with social commentary and a family murder mystery. There were surprisingly lots of similarities with growing up in rural Ireland, and I found this book a really good read. Even if you did not grow up in rural Scotland (or Ireland), I think you’d still enjoy the book; you just might not get all the inside jokes or cultural references.
While I had heard of the author before, I always thought he wrote science fiction books that just didn’t work for me. This was my first time discovering that he wrote non-science fiction also, and I liked this book.
Firefox3.5.5 was released on Thursday 05-nov-2009, at 16:00PST.
This was our fastest turnaround on a release. By far.
From â€œDev says goâ€ to â€œrelease is now available to publicâ€ was approx 3 days (3d 4h 45m) wall-clock time. Release Engineering took 13-16hours. By comparison, the next fastest release turnaround was FF3.5.3 (~37hours) and FF184.108.40.206 (~37hours).
11:13 02nov: Dev says â€œgoâ€ for FF3.5.5
13:06 02nov: FF3.5.5 builds started
17:05 02nov: FF3.5.3 linux, mac builds handed to QA
20:03 02nov: FF3.5.3 signed-win32 builds handed to QA
00:28 03nov: FF3.5.3 update snippets available on test update channel
22:00 04nov: Dev & QA says “go” for Beta, and for Release; Build already completed final signing, bouncer entries
07:30 05nov: mirror replication started
10:55 05nov: mirror absorption good enough for testing
14:40 05nov: website changes finalized and visible. Build given “go” to make updates snippets live.
14:51 05nov: update snippets available on live update channel
16:00 05nov: release announced
1) As we continue streamlining this process, now the long pole is communication between the groups, and also how the websites release notes are assembled and published. For this release, there were
8.5 9.5 hours of waiting between “go to mirrors” and “mirror push started”. Most of Thursday was spent updating release notes on websites. Meanwhile, we populated the mirrors, which takes ~3.5 hours of watching mirrors, but only took two brief commands on our part.
3) Our blow-by-blow scribbles are public, so the curious can read all about it here. Those Build Notes also link to our tracking bug#525814.
This super-super fast release turnaround was handled calmly and efficiently. It was a real credit to the team to see how well everyone worked well together on this, including smooth handoffs back-and-forth across timezones so everyone still had a life ! 🙂
- The numbers for this month are:
- 1,692 code changes to our mercurial-based repos, which triggered:
- 20,887 build jobs, or ~90 jobs per hour.
- 46,219 unittest jobs, or ~62 jobs per hour.
- 42,873 talos jobs, or ~57 talos jobs per hour.
- This was our 2nd busiest recorded month, only slightly below last month’s record high.
- The busiest day was 6th October, with 102 checkins. For comparison, this high level was only exceeded on 22nd Sept (116 checkins) and 20th May (108 checkins).
- The number of unittest and performance jobs run has increased significantly. This is because a) we added new suites, b) we enabled existing suites on more branches and c) we split some suites into smaller, quicker, self-contained suites.
- We are still not tracking down any l10n repacks, nightly builds, release builds or any “idle-timer” builds.
Here’s how it looks compared to the year so far:
Detailed breakdown is :
Here’s how the math works out:
The types of build, unittest and performance jobs triggered by each individual push are best described here.
Everytime someone does a checkin, we do a whole bunch of builds, unittests and performance runs. Sure. But did you know we run about 40 hours worth on desktops, with an additional 25 hours on mobile?
Chris AtLee put together a complete list here, listing out what jobs are run. Its much easier to read then anything I’ve tried in the past, and well worth a quick read.
Its hard to grasp the scale of all this by looking at Tinderbox waterfall, but mstange’s TinderBoxPushLog does a *great* job of showing what happens with every checkin. After you read Chris’s blogpost, all those cryptic code on the right hand side of TinderBoxPushLog will make much more sense!
isthetreegreen.com was a quick-and-easy way for Mozilla developers to tell the state of the tree with a simple “Yes/No/Maybe”. There are lots of more detailed dashboards, but this site distilled all that info down to a simple one word.
isthebaybridgeopen.com is looking to do the same for local commuters. Even the font looks the same! I love how people in this area cope with big setbacks like this. 🙂
(For those of you not familiar with local bay area news, a bridge here is closed for emergency repairs. Its used by 280,000+ cars per day, so this is messing with local commute traffic patterns in a big way. More details here.)