|
1 | | -# Torrust Tracker Release Process (draft) |
| 1 | +# Torrust Tracker Release Process (draft 2) |
2 | 2 |
|
3 | 3 | The purpose of this document is to describe the release process. |
4 | 4 |
|
5 | 5 | ## Overview |
6 | 6 |
|
7 | | -Torrust Tracker is published in this order: |
| 7 | +Torrust Tracker is published according to this protocol: |
8 | 8 |
|
9 | | -1. `develop` branch is ready for publishing. |
10 | | -2. create `release: version (semantic version)` commit. |
11 | | -3. push release commit to `main` branch. |
12 | | -4. check all status checks succeed for `main` branch. |
13 | | -5. push `main` branch to `releases\v(semantic version)` branch. |
14 | | -6. check all status checks success for `releases\v(semantic version)` branch. |
15 | | -7. create signed `v(semantic version)` tag. |
16 | | -8. create github release from `v(semantic version)` tag. |
17 | | -9. merge `main` branch into `develop` branch. |
| 9 | +0. After release create new pull request into `develop` branch: |
| 10 | + |
| 11 | +- The `develop` branch has the (semantic version) suffix `-develop`. |
| 12 | +- The version is bumped according to releases, new features, and breaking changes. |
| 13 | + |
| 14 | +- [ ] `develop` is ready for branching for a release. |
| 15 | +- [ ] force-push develop to `staging` branch. |
| 16 | +- [ ] commit `release: version (semantic version)`, removing the `-develop` suffix. |
| 17 | +- [ ] create pull request to merge `staging` into `main` branch. |
| 18 | +- [ ] check all status checks succeed for `main` branch. |
| 19 | +- [ ] push `main` branch to `releases\v(semantic version)` branch. |
| 20 | +- [ ] check all status checks success for `releases\v(semantic version)` branch. |
| 21 | +- [ ] create signed `v(semantic version)` tag from `releases\v(semantic version) HEAD`. |
| 22 | +- [ ] create github release from `v(semantic version)` tag. |
| 23 | +- [ ] merge the `main` branch back into `develop` branch, assuring that the (semantic version) has the suffix `-develop`. |
18 | 24 |
|
19 | 25 | - At step `1.`, `develop` is automatically published to `dockerhub`. |
20 | 26 | - At step `3.`, `main` is automatically published to `dockerhub`. |
21 | | -- At step `5.`, `releases\v(semantic version)` is automatically published to `dockerhub` and `crate.io`. |
| 27 | +- At step `6.`, `releases\v(semantic version)` is automatically published to `dockerhub` and `crate.io`. |
22 | 28 |
|
23 | 29 | ## Development Branch |
24 | 30 |
|
|
0 commit comments