AndersH asked an important question in comments to my last post., which deserved a proper response, hence this blog post. Thanks AndersH, sorry, I should have been more clear.
We do *today* have a major update offer visible to FF220.127.116.11 users, which will major update them to FF18.104.22.168. A user on FF22.214.171.124 who decided to move to the latest and greatest Firefox would end up going from FF126.96.36.199 -> FF188.8.131.52 -> FF184.108.40.206 -> FF3.0.5 -> FF3.0.7. Thats four updates in a row. Here’s a diagram, which shows what major and minor update offers are currently available, which might help.
The “new process” I was trying to describe above would re-generate a major update offer for the older line every time we did a minor releaseÂ on the newer line. The diagrams look simple enough…
…but the consequences are important. If we could rewind time, and had used the new proposed process, the diagram for today would instead look like this:
It would also mean that:
- The FF220.127.116.11 user would now get to the latest and greatest by going FF18.104.22.168 -> FF22.214.171.124 -> FF3.0.7. Thats only two updates in a row, not four.
- User would be able to see those major update offers more often, so motivated users would more often be *able* to major update.
- Any FF126.96.36.199 users who hit “Later” on a major update offer would be reprompted with a new major update offer every time we produce a new FF3.0.x dot-release. (approx 4-6 weeks).
- Any FF188.8.131.52 user who hit “Never” on a major update offer would never be reprompted for any new major update offer, even when we produce new major updates.
Hope that clarifies. Thanks again AndersH for the excellent question, and again, sorry for not being more clear the first time.
UPDATE: Thanks to nthomas for correctly pointing out that the FF184.108.40.206 major update goes to FF220.127.116.11, not FF18.104.22.168. Updated text, and diagrams. joduinn 16mar2009.