nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-09-20 13:06:20 +02:00
Code Issues Packages Projects Releases Wiki Activity

doc: Minor restructure for Release Lifecycle

Browse Source 
* make end and beginning of life into second-level sections
* write an intro for beginning
* tweak intro for end
This commit is contained in:
teor 2020-04-03 22:06:27 +10:00
parent 0f10ddaa29
commit 6db2e59f20
No known key found for this signature in database
GPG Key ID: 10FEAA0E7075672A
1 changed files with 16 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
doc/HACKING/ReleaseSeriesLifecycle.md
View File

@ -1,9 +1,14 @@
## End of Life on an old release series # Release Series Lifecycle
## End Of Life On An Old Release Series
Here are the steps that the maintainer should take when an old Tor release Here are the steps that the maintainer should take when an old Tor release
series reaches End of Life. Note that they are _only_ for an entire series series reaches End of Life.
that has reached its planned EOL: they do not apply to security-related
deprecations of individual versions. Note that they are _only_ for an entire series that has reached its planned
EOL: they do not apply to security-related deprecations of individual
patch versions.
### 1. Preliminaries ### 1. Preliminaries
@ -17,7 +22,7 @@ deprecations of individual versions.
packagers. packagers.
### 2. On the day ### 2. On The Day
1. Open tickets to remove the release from: 1. Open tickets to remove the release from:
- the jenkins builds - the jenkins builds
@ -72,8 +77,13 @@ deprecations of individual versions.
12. Finally, make sure this document is up to date with our latest 12. Finally, make sure this document is up to date with our latest
process. process.
## Starting A New Release Series
### 3. Starting a new release series. Here are the steps that the maintainer should take to start new maint and
release branches for a stable release.
Note that they are _only_ for an entire series, when it first becomes stable:
they do not apply to security-related patch release versions.
(Ideally, do this immediately after a release.) (Ideally, do this immediately after a release.)