When devedition builds were created, they superceded the devedition builds. The documentation needs to be updated to reflect this here https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded_Builds See bug 1390751 and bug 1391283. The devedition beta builds are here https://tools.taskcluster.net/index/gecko.v2.mozilla-beta.latest.devedition On release, the addon-devel builds are still there, Upon the next uplift when they will be removed and replaced with devedition.
Will these builds auto-update, or will they be functionally equivalent to the unbranded builds that allow signing overrides for beta and release?
They auto update to new dev-edition builds. In devedition about:config the xpinstall.signatures.required can be toggled to False to test unsigned addons.
Summary: documentation needs to be updated to reflect that addon devel builds have been superceded by dev edition builds → documentation needs to be updated to reflect that addon devel builds have been superseded by dev edition builds
Kev, any progress her?
So to clarify as requested by kev via a conversation with catlee, we won't remove the addon-devel builds on release, they will remain there since the devedition builds are only available on m-b. So the documentation can still still reference them for m-r.
You need to log in before you can comment on or make changes to this bug.