This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Improve release process #981
Description
Right now there are too many manual steps in making a release. We should automate:
- Checking that the Travis build is green for a given branch.
- Updating the various install.rdf and manifest.json with the given version.
- Creating release tags for Firefox and Chrome.
- Getting latest translations from Transifex.
- Verifying that reproducible builds still work, i.e. that the hash from the latest Travis build matches the hash when built locally.
- Opening correct upload URLs for Chrome Web Store, Opera add-ons, and addons.mozilla.org.
Reacted by J0WI
Activity
J0WI commentedon Dec 22, 2017
linking to #13716
Hainish commentedon Jan 25, 2018
Some of this was resolved in the migration to WebExtensions. For instance, we have only one tag now, not a separate one for Firefox and Chrome. Firefox also removed the ability to use a key owned by the extension developer for extension signing (unfortunately), which makes the signing process only applicable to Chrome.
This problem will also be alleviated, but not solved, with the delivery of rulesets out-of-band from the extension itself: #12606
jeremyn commentedon Jan 25, 2018
@Hainish I think the only improvement out-of-band updates offers is that you'll be doing less full builds, but each full build will take just as many manual steps as it does now, is that right? Plus you'll have to make a new build process for the OOB updates. (It might be worth documenting what the OOB build process will be, in advance, to flush out problems now.)
Hainish commentedon Jan 25, 2018
@jeremyn
sign-rulesetsdoes not change the extension release process but will give us the option to lengthen the time between builds in the future.J0WI commentedon Feb 26, 2018
linking to #457
Hainish commentedon Jun 17, 2019
With out-of-band rulesets and WebExtensions support in Firefox this pain point has been greatly alleviated. We only need to make new releases on major changes or bugfixes, otherwise a simple weekly ruleset release process suffices. Closing.