Skip to content

Commit

Permalink
docs: document how to create a public Firefox release
Browse files Browse the repository at this point in the history
While this is a maintainers-only task, it is error prone. To avoid
errors, we document the process.

Signed-off-by: Felix Moessbauer <[email protected]>
  • Loading branch information
fmoessbauer committed Jul 2, 2024
1 parent a3e5e4a commit 3bef141
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,3 +53,14 @@ following:
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

## Maintainers: Create Releases

The creation of public releases is a partially automated process:

1. update code and create release tags: `VERSION=<x.x.x> make release`
2. push to GitHub: `git push && git push v<x.x.x>`
3. wait for release action to finish (public release is created)
4. download signed xpi artifact
5. update release information in `.pages/firefox/updates.json`
6. commit updated release information to master

0 comments on commit 3bef141

Please sign in to comment.