forked from M-Labs/artiq
RELEASING: reminder to close GH milestones
This commit is contained in:
parent
c7de233208
commit
a87031f8c3
|
@ -15,7 +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.
|
10. "Draft a new release" and close the milestone on GitHub.
|
||||||
|
|
||||||
Minor (bugfix) releases
|
Minor (bugfix) releases
|
||||||
-----------------------
|
-----------------------
|
||||||
|
@ -23,4 +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.
|
4. "Draft a new release" and close the milestone on GitHub.
|
||||||
|
|
Loading…
Reference in New Issue