diff options
| author | Nick Mathewson <nickm@torproject.org> | 2018-11-24 20:03:48 -0500 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2018-11-24 20:44:37 -0500 |
| commit | b16d6453adde2b13d2aa95a74ec3c09a259f185f (patch) | |
| tree | 6a642bf80eb9bce36e55ee7a2c7e022a292be7be /doc/HACKING/ReleasingTor.md | |
| parent | 3741f9e524a2d3bd7239ca865d6169fd1e3dddb5 (diff) | |
| download | tor-b16d6453adde2b13d2aa95a74ec3c09a259f185f.tar.gz tor-b16d6453adde2b13d2aa95a74ec3c09a259f185f.zip | |
Rewrite updateVersions script in Python, add datestamp functionality.
This updateVersions.pl script was one of the only essential perl
scripts left in out maint system, and was the only one that used
autoconf to fill in the script.
This script adds a feature to define an APPROX_RELEASE_DATE macro
that is updated when the version changes. We'll use this to
implement prop297, so that we have an accurate view of when a
release date happens.
Diffstat (limited to 'doc/HACKING/ReleasingTor.md')
| -rw-r--r-- | doc/HACKING/ReleasingTor.md | 6 |
1 files changed, 1 insertions, 5 deletions
diff --git a/doc/HACKING/ReleasingTor.md b/doc/HACKING/ReleasingTor.md index b5444afa96..b260cdbb19 100644 --- a/doc/HACKING/ReleasingTor.md +++ b/doc/HACKING/ReleasingTor.md @@ -131,13 +131,9 @@ new Tor release: === III. Making the source release. 1. In `maint-0.?.x`, bump the version number in `configure.ac` and run - `perl scripts/maint/updateVersions.pl` to update version numbers in other + `make update-versions` to update version numbers in other places, and commit. Then merge `maint-0.?.x` into `release-0.?.x`. - (NOTE: To bump the version number, edit `configure.ac`, and then run - either `make`, or `perl scripts/maint/updateVersions.pl`, depending on - your version.) - When you merge the maint branch forward to the next maint branch, or into master, merge it with "-s ours" to avoid a needless version bump. |