diff options
Diffstat (limited to 'doc/HACKING/ReleasingTor.md')
| -rw-r--r-- | doc/HACKING/ReleasingTor.md | 35 |
1 files changed, 26 insertions, 9 deletions
diff --git a/doc/HACKING/ReleasingTor.md b/doc/HACKING/ReleasingTor.md index 12f5d1b16b..86feef754e 100644 --- a/doc/HACKING/ReleasingTor.md +++ b/doc/HACKING/ReleasingTor.md @@ -6,7 +6,7 @@ pipeline. Before we begin, first rule is to make sure: - - Our CI pass for each version to release + - Our CIs (*nix and Windows) pass for each version to release - Coverity has no new alerts ## 0. Security Release @@ -20,7 +20,7 @@ prior to the release: ## 1. Preliminaries -The following must be done 2 days at the very least prior to the release: +The following must be done **2 days** at the very least prior to the release: 1. Add the version(s) in the dirauth-conf git repository as the RecommendedVersion and RequiredVersion so they can be approved by the @@ -62,10 +62,15 @@ reproducible way using: https://gitlab.torproject.org/tpo/core/tor-ci-reproducible -Simply run the `./build.sh` which will commit interactively the signature for -you. You then only need to git push. +Steps are: -Once all signatures have been committed: + 1. Run `./build.sh` which will download everything you need, including the + latest tarballs from the release CI, and auto-commit the signatures if + the checksum match. You will need to confim the commits. + + 2. If all is good, `git push origin main` your signatures. + +Once all signatures from all selected developers have been committed: 1. Manually trigger the `signature` job in the `Post-process` stage of the CI release pipeline. @@ -95,20 +100,32 @@ Once all signatures have been committed: Once the tarballs have been uploaded and are ready to be announced, we need to do the following: - 1. Merge upstream the artifacts from the `patches` job in the + 1. Tag versions (main and maint) using `git tag -s tor-0.x.y.z-<status>` + and then push the tags: `git push origin --tags` + + 2. Merge upstream the artifacts from the `patches` job in the `Post-process` stage of the CI release pipeline. - 2. Write and post the release announcement for the `forum.torproject.net` + 3. Write and post the release announcement for the `forum.torproject.net` in the `News -> Tor Release Announcement` category. - Mention in which Tor Browser version (with dates) the release will be - in. This usually only applies to the latest stable. + If possible, mention in which Tor Browser version (with dates) the + release will be in. This usually only applies to the latest stable. + + 4. Inform `tor-talk@lists.torproject.org` with the releasing pointing to + the Forum. Append the ChangeLog there. We do this until we can automate + such post from the forum directly. ### New Stable 1. Create the `maint-x.y.z` and `release-x.y.z` branches and update the `./scripts/git/git-list-tor-branches.sh` with the new version. + 2. Add the new version in `./scripts/ci/ci-driver.sh`. + + 3. Forward port the ChangeLog and ReleaseNotes into main branch. Remove any + change logs of stable releases in ReleaseNotes. + ## Appendix: An alternative means to notify packagers |