You need to install the full version of the current beta release if you want to switch channels. You can't do that otherwise.

Note that the beta channel receives updates twice a week and if it reaches the release candidate state then possibly more often in case more than one RC is required.

• https://www.mozilla.org/en-US/firefox/beta/all/
• https://www.mozilla.org/en-US/firefox/beta/

Shadoefax said

I am currently running Fx Dev Edition 42.0a2 (2015-08-16). It updated today. In fact, it updates every day like I am on the nightly channel. I don't want to develop my extensions with the "bleeding edge" Fx version - it's too unstable. How can I change to the 'beta' channel and get updates only every six weeks or so? I've already changed the pref app.update.channel from 'aurora' to 'beta' but it doesn't seem to make a difference. In fact, it changes back to 'aurora' after every update.

The Aurora (aka Developer Edition) channel like Nightly gets checkins almost everyday so therefore they get updates each of those days with the occasional respins.

The Beta channel is more stable as it generally gets six to twelve Beta builds for a version.

Changing the app.update.channel in about:config will have zero affect. You need to modify a file. However this only works in moving forward a channel (say Beta to Aurora) and not well back a channel.

The Beta builds of Firefox 41.0 (currently still at 41.0b1) https://www.mozilla.org/firefox/channel/#beta https://www.mozilla.org/en-US/firefox/beta/all/ (full setups for Windows)

While there has been Win64 builds on Beta channel since 37.0b2, the Firefox 41.0 may be the first Release to have Win64 build. Unless it changes as it was originally planned briefly to have Win64 for Fx 40.0 Release.

But is 41.0b1 available in the Developer Edition? I need to develop my extensions without being signed during the writing/debugging stage.

You can disable signing up until RC if I recall correctly. I just tested turning XPI signing off successfully. Not sure if you know the setting in about:config, so set the following.

xpinstall.signatures.required; false

My own extensions work fine in the current beta with xpinstall.signatures.required = false. That will be a problem once this pref gets removed on the current release and you would have to use a special unbranded version.

It would have been better if the release and beta channel would have support for this pref, but that it would only have effect when locked to false, so it can't be changed to true by Firefox and not when you would manually set the pref to false on the about:config page.

For Firefox 41.0 you can disable it in about:config still however as of Firefox 42.0 on Release and Beta channel then you will not be able to disable this.

Firefox 40: Firefox warns about signatures but doesn't enforce them. Firefox 41: Firefox will have a preference that allows signature enforcement to be disabled (xpinstall.signatures.required in about:config). Firefox 42: Release and Beta versions of Firefox 42.0 will not allow unsigned extensions to be installed, with no override.

https://wiki.mozilla.org/Addons/Extension_Signing Only Extensions as themes, dictionaries, language packs, and plugins don't need to be signed.

Shadoefax said

But is 41.0b1 available in the Developer Edition? I need to develop my extensions without being signed during the writing/debugging stage.

Release, Beta, Aurora (Developer Edition) and Nightly are separate channels.

The b1 means it is the first Beta build of that version.

I just installed Fx v41.0b1 and am able to install unsigned extensions. All seems to work fine. I'm assuming that if I stay on the beta update channel, I will always get updated with betas only - never the final stable release. That is fine because I will only be using this install for development. I guess I'll just uninstall the Dev Edition completely - hated the dark, gloomy theme anyway ;) Thank you for your help.

If you stay on Beta channel then you will eventually get 42.0b1 after when Firefox 41.0 is Released.

James said

For Firefox 41.0 you can disable it in about:config still however as of Firefox 42.0 on Release and Beta channel then you will not be able to disable this.

So, in other words, as of Fx 42 we developers will be forced to develop our extensions in volatile, unstable environment. Lovely.

• https://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/

• There will be a transition period of two release cycles (12 weeks total) during which unsigned extensions will only generate a warning in Firefox.

• After the transition period, it will not be possible to install unsigned extensions in Release or Beta versions of Firefox. There won’t be any preferences or command line options to disable this.

• Installation of unsigned extensions will still be possible on Nightly and Developer Edition, as well as special, unbranded builds of Release and Beta that will be available mainly for developers testing their extensions.

cor-el said

Installation of unsigned extensions will still be possible on Nightly and Developer Edition, as well as special, unbranded builds of Release and Beta that will be available mainly for developers testing their extensions.

Are these builds available now? Do you have a link?

There is currently no need for such a special version because you still have the xpinstall.signatures.required pref in the current beta (default: true) and in the current release this pref defaults to false.

James said

If you stay on Beta channel then you will eventually get 42.0b1 after when Firefox 41.0 is Released.

So ... bottom line ... if one wants to develop extensions for Fx you must use and test in a "not ready for prime time" browser that is updated on a daily basis. If an error comes up, you'll have to decide if it is a problem with your extension's code, or a problem with Firefox. If something works today, it may not tomorrow. Nothing good will come from this. I just hope those "special, unbranded builds of Release and Beta" will be available soon.