From bbc4185737b797e2f48322afd4b2eb6034554213 Mon Sep 17 00:00:00 2001 From: Sebastien Bourdeauducq Date: Fri, 27 Jan 2017 21:37:30 +0800 Subject: [PATCH] RELEASING: mention GitHub releases --- RELEASING.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/RELEASING.rst b/RELEASING.rst index c81a46be4..31624c4df 100644 --- a/RELEASING.rst +++ b/RELEASING.rst @@ -15,6 +15,7 @@ Major releases 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. 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 ----------------------- @@ -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). 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. +4. "Draft a new release" on GitHub.