Opened 8 months ago

Closed 6 weeks ago

#28453 closed task (fixed)

Create a EndOfLifeTor.md document

Reported by: teor Owned by: nickm
Priority: Low Milestone: Tor: 0.4.1.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-doc, release-management, postfreeze-ok, 041-should, asn-merge
Cc: Actual Points:
Parent ID: Points:
Reviewer: dgoulet Sponsor:

Description

We have instructions for releasing tor:
https://gitweb.torproject.org/tor.git/tree/doc/HACKING/ReleasingTor.md

But we don't have any instructions for deprecating tor.

Child Tickets

Change History (20)

comment:1 Changed 8 months ago by teor

Cc: dgoulet added
Status: newneeds_review

See my draft "End of Life Tor" instructions in:
https://github.com/torproject/tor/pull/509

comment:2 Changed 8 months ago by teor

Summary: Create a DeprecatingTor.md documentCreate a EndOfLifeTor.md document

comment:3 Changed 8 months ago by dgoulet

Status: needs_reviewneeds_revision

Good stuff! Two comments, easy changes. Very nice document to have!

comment:4 Changed 8 months ago by nickm

Does this cover only the deprecation of an entire release series, or does it cover the case where we want to un-recommend older releases within a series?

Do we want to accelerate this schedule if there's a security issue?

comment:5 in reply to:  4 Changed 8 months ago by dgoulet

Replying to nickm:

Does this cover only the deprecation of an entire release series, or does it cover the case where we want to un-recommend older releases within a series?

Afaict, an entire series. This is really about the EOL of a major number version (ex: 0.3.2.x)

Do we want to accelerate this schedule if there's a security issue?

I don't think accelerating the EOL of a series because of a security issue is in scope of this document. That should probably be detailed in our "security policy" document *if* we judge that it could arise one day that we fast track EOL.

comment:6 Changed 8 months ago by nickm

Okay. So in that case, let's have document describe itself as only applying to the planned deprecation of an entire release series.

comment:7 Changed 6 months ago by nickm

Keywords: postfreeze-ok added

Mark some tickets as postfreeze-ok, to indicate that I think they are okay to accept in 0.4.0 post-freeze. Does not indicate that they are all necessary to do postfreeze.

comment:8 Changed 5 months ago by dgoulet

Keywords: 040-can added
Priority: MediumLow

Bug triage of 0.4.0 tickets. These are now in the "CAN" section. Lower priority than "040-must".

comment:9 Changed 5 months ago by nickm

Owner: set to dgoulet
Status: needs_revisionassigned

comment:10 Changed 5 months ago by nickm

Status: assignedneeds_revision

comment:11 Changed 5 months ago by dgoulet

Cc: dgoulet removed
Owner: changed from dgoulet to teor
Status: needs_revisionassigned

comment:12 Changed 5 months ago by dgoulet

Status: assignedneeds_revision

comment:13 Changed 2 months ago by nickm

Keywords: 041-should added; 040-can removed
Owner: changed from teor to nickm
Status: needs_revisionaccepted

comment:14 Changed 2 months ago by nickm

Milestone: Tor: 0.4.0.x-finalTor: 0.4.1.x-final

comment:15 Changed 7 weeks ago by nickm

Status: acceptedneeds_review

I've rebased this on master, and done the revisions for it as ticket28453_v2. PR at https://github.com/torproject/tor/pull/1062 . Thanks to teor for the original work here and dgoulet for comments.

comment:16 Changed 7 weeks ago by asn

Reviewer: dgoulet

comment:17 Changed 7 weeks ago by dgoulet

Keywords: asn-merge added
Status: needs_reviewmerge_ready

comment:18 Changed 6 weeks ago by asn

Status: merge_readyneeds_revision

I'm getting merge conflicts with master here. This should be merged on master right, not 041, correct? Marking as needs_revision becasue of the conflicts.

comment:19 Changed 6 weeks ago by nickm

Status: needs_revisionmerge_ready

ok, please see branch ticket28453_v2_merged, which resolves the conflict. PR at https://github.com/torproject/tor/pull/1102

comment:20 Changed 6 weeks ago by asn

Resolution: fixed
Status: merge_readyclosed

Merged!

Note: See TracTickets for help on using tickets.