nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-10 05:03:43 +01:00
Code Issues Packages Projects Releases Wiki Activity

doc: Update ReleasingTor.md with missing steps

Browse Source 
Signed-off-by: David Goulet <dgoulet@torproject.org>
This commit is contained in:
David Goulet 2021-12-16 12:14:52 -05:00
parent 475d669f62
commit a81ddc83be
1 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/HACKING/ReleasingTor.md
View File

@ -100,20 +100,28 @@ Once all signatures from all selected developers 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.
### 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