Updated Release Process (markdown)

Brendan Dahl 2014-04-10 10:20:40 -07:00
parent fa74d20cab
commit 9342b8dff3

@ -1,10 +1,12 @@
Overview: Release a version every six weeks. Ideally this should be one week before Firefox uplift dates, see https://wiki.mozilla.org/RapidRelease/Calendar
1. [Update pdf.js on mozilla central.](https://github.com/mozilla/pdf.js/wiki/Updating-pdf.js-on-Mozilla-Central)
1. Get review. If there's feedback, fix it and return to step 1.
1. Update the AMO addon with the final reviewed version from above.
1. Create a tag and push it github.
```
git tag v0.4.11 -m "v0.4.11 Firefox 17"
git push upstream v0.4.11
```
1. `git checkout <SHA IN MOZ CENTRAL>`
1. Run `node make dist` to generate the zip and update pdfjs.confg
1. Create a PR with pdfjs.config changes
1. Create github release
2. add release notes
2. attach zip generated from above
2. mark as pre-release
1. Remove pre-release flag from previous beta release
1. Eat cake