commit 43ce4626f1c23f723a3007e91cfb1ed5f8a75712 Author: Nick Mathewson nickm@torproject.org Date: Thu Nov 5 09:46:40 2015 -0500

add release notes --- doc/HACKING/ReleasingTor.md | 10 ++++++++++ 1 file changed, 10 insertions(+)

diff --git a/doc/HACKING/ReleasingTor.md b/doc/HACKING/ReleasingTor.md index 12a0765..845a61b 100644 --- a/doc/HACKING/ReleasingTor.md +++ b/doc/HACKING/ReleasingTor.md @@ -68,6 +68,16 @@ Here are the steps Roger takes when putting out a new Tor release: to a release-0.2.x branch, manually commit the changelogs to the later git branches too.

+ If you're doing the first stable release in a series, you need to + create a ReleaseNotes for the series as a whole. To get started + there, copy all of the Changelog entries from the series into a new + file, and run `./scripts/maint/sortChanges.py` on it. That will + group them by category. Then kill every bugfix entry for fixing + bugs that were introduced within that release series; those aren't + relevant changes since the last series. At that point, it's time + to start sorting and condensing entries. (Generally, we don't edit the + text of existing entries, though.) + 4. In `maint-0.2.x`, bump the version number in `configure.ac` and run `scripts/maint/updateVersions.pl` to update version numbers in other places, and commit. Then merge `maint-0.2.x` into `release-0.2.x`.