Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Tor
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Container Registry
Model registry
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
Core
Tor
Commits
6263d9e1
Commit
6263d9e1
authored
6 years ago
by
teor
Committed by
Nick Mathewson
5 years ago
Browse files
Options
Downloads
Patches
Plain Diff
doc: Add End of Life Tor instructions
Closes 28453.
parent
c390f1dd
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/HACKING/EndOfLifeTor.md
+52
-0
52 additions, 0 deletions
doc/HACKING/EndOfLifeTor.md
with
52 additions
and
0 deletions
doc/HACKING/EndOfLifeTor.md
0 → 100644
+
52
−
0
View file @
6263d9e1
End of Life on an old release series
------------------------------------
Here are the steps that the maintainer should take when an old Tor release
series reaches End of Life:
=== 0. Preliminaries
0.
A few months before End of Life:
Write a deprecation announcement.
Send the announcement out with every new release announcement.
1.
A month before End of Life:
Send the announcement to tor-announce, tor-talk, tor-relays, and the
packagers.
2.
A few days before End of Life:
Get at least two of weasel/arma/Sebastian to
remove the old version number from their approved versions list.
Give them a few days to do this if you can.
=== 1. On the day
1.
Open tickets to remove the release from:
-
the jenkins builds
-
tor's Travis CI cron jobs
-
chutney's Travis CI tests (#)
-
stem's Travis CI tests (#)
2.
Close the milestone in Trac. To do this, go to Trac, log in,
select "Admin" near the top of the screen, then select "Milestones" from
the menu on the left. Click on the milestone for this version, and
select the "Completed" checkbox. By convention, we select the date as
the End of Life date.
3.
Replace NNN-backport with NNN-unreached-backport in all open trac tickets.
4.
If there are any remaining tickets in the milestone:
-
merge_ready tickets are for backports:
-
if there are no supported releases for the backport, close the ticket
-
if there is an earlier (LTS) release for the backport, move the ticket
to that release
-
other tickets should be closed (if we won't fix them) or moved to a
supported release (if we will fix them)
5.
Double-check: did the version get un-recommended in the consensus yet?
If not, don't announce until they have the up-to-date versions, or people
will get confused.
6.
Mail the end of life announcement to tor-announce, the packagers list,
and tor-relays. The current list of packagers is in ReleasingTor.md.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment