#28265 closed enhancement (implemented)

Should Tor 0.3.5 be the last 0.3.x since it's an LTS?

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: 0.4.0.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Tor 0.2.9 was the final Tor on the 0.2.x branch, and it was an LTS.

We could follow that pattern and move from 0.3.5 to 0.4.0.

The only downside I can see is that we hasten our arrival to Tor 1.0.0. But is that so bad?

Child Tickets

Change History (4)

comment:1 in reply to:  description Changed 15 months ago by dgoulet

Replying to arma:

Tor 0.2.9 was the final Tor on the 0.2.x branch, and it was an LTS.

We could follow that pattern and move from 0.3.5 to 0.4.0.

+1

The only downside I can see is that we hasten our arrival to Tor 1.0.0. But is that so bad?

Going towards 1.0.0 is fine imo. It will happen one day anyway. Considering we do 2 releases a year... we still have a long way to get there if we follow the 0.x.y pattern.

comment:2 Changed 15 months ago by nickm

I am fine with this.

comment:3 Changed 15 months ago by nickm

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

Tor 0.3.6.x has been renamed to 0.4.0.x.

comment:4 Changed 12 months ago by nickm

Resolution: implemented
Status: newclosed

Done; we decided to name the series after 0.3.5 as 0.4.0.

Note: See TracTickets for help on using tickets.