Document the release procedure #345
Conversation
README.md
Outdated
|
|
||
| We don't use `zest.releaser` right now because of some problems with | ||
| releasing a package that is not at the root of the repo (`jobs/`), but | ||
| this could change if we figure out how. |
There was a problem hiding this comment.
I think it's also because we don't really need pypi. It runs in a lambda that we publish as a zip on the release page
There was a problem hiding this comment.
Ah right, I forgot to mention about the release page, thanks.
|
It's been a while since I wrote this but it's really served me well. Whenever I want to upgrade Stage I just type It's good to have instructions but it's sometimes even better to have it all automated away. |
|
What I'm suggesting is that we look at that |
|
I agree that it's valuable to have these processes automated. Let's look into what it would take to get zest.releaser working on this project, and extending it with hooks to do the Github/Bugzilla bits. I've opened #346 about this. |
README.md
Outdated
| The current procedure is: | ||
|
|
||
| * Bump version in `jobs/setup.py` | ||
| * `git tag x.y.z` |
There was a problem hiding this comment.
What about updating the release date in the CHANGELOG.rst and running make build-dependencies
| * `git tag x.y.z` | ||
| * `git push --tags origin` | ||
| * `make lambda.zip` | ||
| * Add a release on Github with the lambda.zip attached |
There was a problem hiding this comment.
What does this mean? Going to https://github.com/mozilla-services/buildhub/releases/new and manually upload the lambda.zip file with the browser?
There was a problem hiding this comment.
Based on previous releases, I think so, but I've never done it myself.
There was a problem hiding this comment.
Yes, manual upload so far.
README.md
Outdated
| * `git push --tags origin` | ||
| * `make lambda.zip` | ||
| * Add a release on Github with the lambda.zip attached | ||
| * Open a ticket like https://bugzilla.mozilla.org/show_bug.cgi?id=1426340 to get it deployed |
There was a problem hiding this comment.
So, the only variable is the tag name?
A link to create the bug can be made with this as a query string variable.
See how the "Bugzilla" tab on Crash-stats have links to enter a new bug with lots of the stuff already filled in.
https://crash-stats.mozilla.com/report/index/19ef17b4-3864-4a55-b9a6-ae6e30180204#tab-bugzilla
Thanks @peterbe for the suggestion.
I've found instructions like these incredibly helpful in Kinto-related projects. This is just the set of steps I understood from Mathieu in chat this morning.