Skip to content

Commit da44446

Browse files
committed
update release procedure - delete obsolete, add patch release
1 parent 4636d9e commit da44446

File tree

1 file changed

+21
-6
lines changed

1 file changed

+21
-6
lines changed

docs/development.md

Lines changed: 21 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,26 @@ Bugs go to [JIRA](https://its.cern.ch/jira/projects/OCTRL/issues).
88

99
## Release Procedure
1010

11+
### Major releases
12+
1113
1. Update documentation if necessary.
1214
2. Bump `VERSION` file, commit, push (or pull request).
13-
3. Run `hacking/release_notes.sh HEAD` to get a formatted commit message list since the last tag, copy it.
14-
4. Paste the above into a [new GitHub release draft](https://github.com/AliceO2Group/Control/releases/new). Sort, categorize, add summary on top.
15-
5. Pick a version number. Numbers `x.x.80`-`x.x.89` are reserved for Alpha pre-releases. Numbers `x.x.90`-`x.x.99` are reserved for Beta and RC pre-releases. If doing a pre-release, don't forget to tick `This is a pre-release`. When ready, hit `Publish release`.
16-
6. Go to your local clone of `alidist`, ensure that the branch is `master` and that it's up to date. Then branch out into `aliecs-bump` (`git branch aliecs-bump`).
17-
7. Bump the version in `control.sh`, `control-core.sh`, `control-occplugin.sh` and `coconut.sh`. Commit and push to `origin/aliecs-bump` (`git push -u origin aliecs-bump`).
18-
8. Submit pull request with the above to `alisw/alidist`.
15+
3. Go to a [new GitHub release draft](https://github.com/AliceO2Group/Control/releases/new). Use "Generate release notes" to create a list of changes. Write a short summary at the top.
16+
4. Go to your local clone of `alidist`, ensure that the branch is `master` and that it's up to date. Then branch out into `aliecs-bump` (`git branch aliecs-bump`).
17+
5. Bump the version in `control.sh`, `control-core.sh`, `control-occplugin.sh` and `coconut.sh`. Commit and push to `origin/aliecs-bump` (`git push -u origin aliecs-bump`).
18+
6. Submit pull request with the above to `alisw/alidist`.
19+
20+
### Patch releases
21+
22+
1. Update documentation if necessary.
23+
2. If the patch release should NOT be based on master:
24+
25+
* Checkout the tag which the patch release should be based on, e.g. `git checkout v1.34.0`
26+
* Create a branch called `branch_<planned_tag>`, e.g. `git checkout -b branch_v1.34.1`.
27+
28+
3. Bump `VERSION` file, commit, push (or pull request).
29+
4. Go to a [new GitHub release draft](https://github.com/AliceO2Group/Control/releases/new). Use "Generate release notes" to create a list of changes. Write a short summary at the top.
30+
5. Go to your local clone of `alidist`, ensure that the branch is `master` and that it's up to date. Then branch out into `aliecs-bump` (`git branch aliecs-bump`).
31+
6. Bump the version in `control.sh`, `control-core.sh`, `control-occplugin.sh` and `coconut.sh`. Commit and push to `origin/aliecs-bump` (`git push -u origin aliecs-bump`).
32+
7. Submit pull request with the above to `alisw/alidist`.
33+

0 commit comments

Comments
 (0)