Document the release procedure #345
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,3 +10,19 @@ | |
| ## Licence | ||
|
|
||
| Apache 2 | ||
|
|
||
| ## Releasing | ||
|
|
||
| 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/`), and | ||
| because we have no interest in uploading this project to PyPI, but | ||
| this could change if we figure out how. | ||
|
|
||
| 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 |
||
| * `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 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. |
||
| * 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? See how the "Bugzilla" tab on Crash-stats have links to enter a new bug with lots of the stuff already filled in. |
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah right, I forgot to mention about the release page, thanks.