InformAction Forums

If I recall correctly, it used to be the case that users were never updated to a development build, even if they had installed one. Automatic updates only occurred whenever a new release build was available on AMO. Now, whenever a user installs an available development build from http://noscript.net/getit#devel, the user is automatically put on the beta channel and receives an automatic update for each of the development builds -- frequently and perpetually -- until the user manually installs a release build.

This behavior could be irritating for users who installed the development build -- at our urging, e.g. "try the development build" -- to fix a bug or other problem they may be having. We, including Giorgio, have repeatedly assured them that the development build isn't really "experimental", but the latest, greatest, and most stable version of NoScript available. The reasons they aren't pushed as releases to AMO are to prevent overloading the AMO reviewers and to prevent pushing releases to users so often they are irritating. For example:

The latest stable version is always the most current development version, even if it isn't available from AMO yet. Download it from http://noscript.net/getit#devel
From http://forums.informaction.com/viewtopi ... 9867#p9867

Giorgio Maone wrote:Due to my development model, latest dev build is always the best version available (the one I use for my daily browsing).
Unless an outstanding bug or security enhancement is mandatory, though, I try to put at least one week between "stable" releases, since some users find automatic updates rather annoying.

I don't know if there is a practical technical solution to this issue, or even if Giorgio has experienced enough (any?) complaints from users that have started getting too frequent updates all of a sudden. Would it be possible for automatic updating to dev builds be restricted to only those users who got their version from the AMO beta channel -- an explicit opt-in -- but not those users who get it from http://noscript.net/getit#devel? I suppose not. I don't know. If that's not practical, I suggest adding something to http://noscript.net/faq#qa2_6 by changing the relevant section to something like: (changes in bold)

Notice that almost daily builds containing cosmetic bug fixes or experimental features are available from http://noscript.net/getit#devel[b] or the Beta Channel on NoScript AMO[/b], but the updates pushed automatically through the addons.mozilla.org channel are only the "stable" ones, containing either important security features or major functionality additions. If you no longer want to be on the beta channel, just install the current release version from NoScript AMO.

I had literally no complain at all from users gone to the beta channel, maybe because as soon as I realized how "RC" versions were treated by AMO, I I set up them to never show the release notes on startup unless a "stable" version shift happens in the meanwhile (i.e. 2.0rc1, 2.0rc2, 2.0rc3 and so on did not get release notes, while users upgrading from 2.0rc9 to 2.0.1rc1 did).

However the change you propose is correct and useful, so I'm implementing it, thanks.

Giorgio Maone wrote:I had literally no complain at all from users gone to the beta channel,

That's good to hear. I was hoping that's the case.

maybe because as soon as I realized how "RC" versions were treated by AMO, I I set up them to never show the release notes on startup unless a "stable" version shift happens in the meanwhile (i.e. 2.0rc1, 2.0rc2, 2.0rc3 and so on did not get release notes, while users upgrading from 2.0rc9 to 2.0.1rc1 did).

I noticed that. Good move!

However the change you propose is correct and useful, so I'm implementing it, thanks.

You're welcome.

Changes done.

Giorgio Maone wrote:Changes done.

What are the changes? Will noscript.net beta builds have a different update url? To what will they update?

Giorgio has updated the FAQ per my suggestion. I don't know if anything else is changed.

Edit: The xpi files served by the beta channel on AMO and the one from http://noscript.net/getit#devel are byte-by-byte identical. It looks like the only change is in the FAQ, which is OK by me.

al_9x wrote:What are the changes? Will noscript.net beta builds have a different update url? To what will they update?

Just the FAQ.
All beta builds will have the same update URL, i.e. none (defaulting to Mozilla's bouncer).