occheung
/
artiq
forked from M-Labs/artiq
1
0
Fork 0
Code Pull Requests Activity

RELEASING: mention GitHub releases

This commit is contained in:
Sebastien Bourdeauducq 2017-01-27 21:37:30 +08:00
parent e6a8d96b7c
commit 6e641427f0
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
RELEASING.rst
View File

@ -15,6 +15,7 @@ Major releases
7. Tag X.0 in the release-X branch, build it, and copy its packages to ``main`` channel. 7. Tag X.0 in the release-X branch, build it, and copy its packages to ``main`` channel.
8. Mint a new DOI from Zenodo and update the README/introduction. 8. Mint a new DOI from Zenodo and update the README/introduction.
9. Update the m-labs.hk/artiq/manual redirect to point to m-labs.hk/artiq/manual-release-X (edit /artiq/.htaccess). 9. Update the m-labs.hk/artiq/manual redirect to point to m-labs.hk/artiq/manual-release-X (edit /artiq/.htaccess).
10. "Draft a new release" on GitHub.
Minor (bugfix) releases Minor (bugfix) releases
----------------------- -----------------------
@ -22,3 +23,4 @@ Minor (bugfix) releases
1. Backport bugfixes from the master branch or fix bugs specific to old releases into the currently maintained release-X branch(es). 1. Backport bugfixes from the master branch or fix bugs specific to old releases into the currently maintained release-X branch(es).
2. When significant bugs have been fixed, tag X.Y+1. 2. When significant bugs have been fixed, tag X.Y+1.
3. To help dealing with regressions, no new features or refactorings should be implemented in release-X branches. Those happen in the master branch, and then a new release-X+1 branch is created. 3. To help dealing with regressions, no new features or refactorings should be implemented in release-X branches. Those happen in the master branch, and then a new release-X+1 branch is created.
4. "Draft a new release" on GitHub.