We're well aware that the update system we had in place for Firefox 1.0 was sub-par and a major focus for the upcoming 1.1 release has been building a world-class update system that "just works" for our users.
Accomplishing this work is no small feat and we learned a lot from our experiences with the 1.0.x releases. The new system will be much more robust and capable on both the client side and the server side. From the client end, we've got a much improved user experience that should take away pretty much all of the pain of updating Firefox 1.1 for both minor versions and major versions. On the server side, we've increased our capacity and will have the capability to serve "patch" updates which should make things easier for everyone.
This new system will also provide benefits for our testing community. If all (or even most) goes according to plan, nightly build users will be able to get the latest nightly bits through the same update mechanism which will make testing nightly builds a bit more convenient and, more importantly, will help us get a lot more testing on the update system itself. This nightly updating system should be in place within the next few days and will be available to our 1.1 Alpha 2 users (preffed off by default). 1.1 Alpha 2 is just the first testing stage, though, and the 1.1 Beta is where we'll introduce the full set of capabilities (including patching) to the testing community.
I'm super-excited about these improvements and will do my best to keep you all up to date on our progress and the opportunities for early testing. Stay tuned.
Posted by asa at July 2, 2005 12:28 PMI would like to be the first to congratulate for the fantastic achievement. I am glad that you took this as a priority, it was wise decision.
Posted by: Ivan Icin on July 2, 2005 01:09 PMAh brilliant. I was wondering if the update system could be used for nightlies as well. :)
Posted by: David Stone on July 2, 2005 02:06 PMI assume that people using optimised builds (quite fairly) won't have the option of binary patches?
Posted by: Robin on July 2, 2005 04:24 PMto be clear, does the new updater allow you to install new versions without uninstalling the old version first? well, to be clear - i'm a neat freak, so I can't go having FireFox 1.0.3 and FireFox 1.0.4 in my "Add/Remove" control panel at the same time. But, of course, if I uninstall 1.0.3, I can no longer run 1.0.4. So I have to uninstall 1.0.3 before installing 1.0.4.
..... so..... is that fixed?
Asa, while we're on the subject of the update system, can you please check out the following dialog?
Tools > Options > Advanced > Update > Advanced...
I don't know about you, but in a browser which is widely regarded as usable, that's just too much text. I'm about as far from the lay user as you can be and *I* don't want to read it.
Can you get someone on this? It's just silly.
Posted by: Ben Basson on July 2, 2005 04:56 PMjoe Lion: That's https://bugzilla.mozilla.org/show_bug.cgi?id=247884 which was fixed some time ago in development versions of Firefox, so I imagine it would be fine with the new updater.
Posted by: DopefishJustin on July 2, 2005 05:43 PMOne thing I hope the new update system does is pester the user to actually upgrade their browser.
I love how Trillian does it. When you launch it, the first thing it will display (assuming an update is available) is an update dialog telling you to download an update.
That practically guarentees that every Trillian user updates their browser.
I hope Firefox does something similar...we need to get people off of those old versions!
Posted by: Chris G. on July 2, 2005 05:59 PM"nightly build users will be able to get the latest nightly bits through the same update mechanism...[which] should be in place in the next few days and will be available to our 1.1 Alpha 2 users...[but] the 1.1 Beta is where we'll introduce the full set of capabilities (including patching)"
That doesn't make sense to me. How can we d/l the updated bits daily in the next few days, if "patching" isn't available until further down the road?
Posted by: cosmoxl on July 2, 2005 06:16 PMI believe when Asa refers to patched builds, he means the .xpi's that you can download to update your Firefox. What we'll be able to donwnload in the next few days are probably the full builds in the new .mar form that have been in the recent trunk download directories.
Posted by: David Stone on July 2, 2005 06:40 PMBen Basson: yikes! I think the advanced dialog should look more like this:
[x] Ask if some of my extensions will stop working
[x] Ask if my current theme will stop working
[x] Ask for major updates
i quit dealing with the headaches of upgrading at v1.0.
it's working just fine.
this is so overdue. thanks.
Posted by: firq krumpl on July 2, 2005 07:29 PMJesse & Asa: Bug 299507
Posted by: Ben Basson on July 2, 2005 08:26 PMNeato Burito, I've been waiting for this for a while.... it's about time we start hearing more good news.
Posted by: Jmack on July 2, 2005 09:29 PM@joe lion - that bug was fixed with 1.0.4 already
Posted by: Ryan VanderMeulen on July 2, 2005 10:20 PMWon't be of much use it it does not check for updates at Extensions Mirror site ..
I have 47 extensions with 1.04 .... about half are on the "update" site and the other half are only on the Extension Mirror site ... so update never checks these for me ....
With the release of 1.1 .. Extension Mirror site is only going to have those extensions and themes that are NOT on the offical update site ...
if would be nice if the update would check at both sites .... Will it? ... or is Mozilla going to continue to pretend that the only source is the Official site??
Oh, one other thing ... why can you not see more than 10 listing per page at the update site .... check "all" and you have 50+ pages ... what happen to display 50 per page or better yet .... "all" means all ....
later, Richard
Posted by: Richard Martin on July 3, 2005 06:41 AM@ Richard Martin - I think having an official site is most responsible way to check for extensions update. Extensionsmirror is a third party site, not part of the Mozilla Foundation. Now my question - why are half of your extensions not listed on u.m.o? What's stopping the authors from doing so?
Posted by: Ryan VanderMeulen on July 3, 2005 07:52 AMI'm pretty sure the extension update checks at any site the Author places a link to in the extension. It doesn't matter where.
Posted by: Dan on July 3, 2005 10:58 AMAsa for some reason this feed doesnt show up in thunderbird or firefox but the feed from yesterday does though.
Posted by: Kurt on July 3, 2005 11:21 AMHere's an idea: Give third-party builders something that can let them use the patch system on their binaries. I know quite a few of them are (or were) struggling with bandwidth...
Posted by: ant on July 3, 2005 03:05 PMGood to hear about these changes -- it's things that shouldn't be there to be a more competitive browser, to offer enhanced functionality, it's things that simply must be there and work well for many system administrators to take Firefox seriously.
Posted by: Jug on July 3, 2005 03:56 PMhttps://bugzilla.mozilla.org/show_bug.cgi?id=299411#c21
is it true that beast is dead? say it aint so. the only problem i have (and that a bunch of people in peter(6)'s mozillazine thread have) is that the deer park branding just sucks so bad. please tell chase to bring beast back. its still building on the tinderbox page, its just not uploading to the mirrors.
Posted by: no one on July 3, 2005 05:18 PMOOOhhh and it instantly strikes me that this can make it easy to see the difference between new users and regular users who're simply updating, by checking server logs. Creating the benefit of seeing how many new users are taking to Firefox, and how many downloads are just updates by regular users... assuming the update mechanism has a slightly unique browser signature, which it should (unless I completely misunderstand "browser signature theory").
Posted by: Devon on July 3, 2005 07:35 PMOops...I didn't realize that my regular e-mail address would be visible to spambots, could you edit it out of my previous comment?
Posted by: Devon on July 3, 2005 07:37 PMLooking forward to it!
Posted by: Kelson on July 4, 2005 12:25 PM