Developer Edition is a great marketing vehicle. Also, it's Beta a little bit early, so it gives us a good way to get early warnings of Beta problems. We want to continue having Developer Edition, and possibly expand its value proposition. But building this separate product every 6 weeks is expensive (build, l10n, QA, etc.) So, the goal for this meta bug is to investigate removing the requirement for a separate build, i.e. doing a repack of Beta. We attempted to do this last year already (see bug 1354262), but met several roadblocks on the way to ended up being more costly to remove than to continue doing a Beta rebuild. The first step for this bug is to list what would be needed to remove the need for a separate build, and list the roadblocks, here as children bugs.

Where's the best place to get a good summary of devedition specific changes?

(In reply to Mike Kaply [:mkaply] from comment #1) > Where's the best place to get a good summary of devedition specific changes? Notable changes in DevEdition: - Add-on signing verification can be turned off - Legacy add-ons/WebExtension experiments can be installed - Developer toolbar buttons are placed on the toolbar by default - Dark theme is the default theme - It can be ran in parallel with other Firefox channels See: https://searchfox.org/mozilla-central/search?q=MOZ_DEV_EDITION&redirect=false https://searchfox.org/mozilla-central/source/browser/config/mozconfigs/macosx64/devedition

I'm honestly unclear on how we can do some of these as a repack without accidentally "leaking" them in beta. Beta doesn't provide: * Add-on signing verification can be turned off * Legacy add-ons/WebExtension experiments can be installed So we wouldn't want these controlled with a pref or any other user accessible mechanism...

Bug 1460476 is filed on figuring out how to address some of comment 3, FWIW. --> Adding dependency.

You need to loop in RelEng on this too. Given that we do an early rollout of DevEdition builds before we're ready to ship full-on Beta builds (which are published to an entirely different product directory), I worry about us "leaking" beta builds we don't actually want to ship.

Note that tromey had r+'d patches on bug 1354262 that may address a lot of the hypothetical conversion here, aside from the trickier extension-signing stuff tracked in bug 1460476.

Adding Nick Thomas to think about this.