[tor-dev] RFC: Tor long-term support policy

[nusenu]

> == Plan for current releases ==
> 
> 0.2.4.x, 0.2.6.x, and 0.2.7.x, will all receive at least one more
>    stable release.  Support for them will end on 1 August 2017.
> 
> 0.2.8.x will be supported until 1 January 2018.
> 
> 0.2.5.x is retroactively declared an LTS release, and will be
>    supported until 1 May 2018.
> 
> 0.2.9.x is an LTS release, and will be supported until at least
>    1 January 2020.

I'm glad to see such a policy.

Maybe be more verbose on when tor dir auths plan to remove EOL tor
relays from consensus?

+---------------------+
| relays_published    |
+---------------------+
| 2017-01-17 07:00:00 |
+---------------------+
+-------------+-------------+-----------+------------+--------+
| tor version | cw-fraction | exit_prob | guard_prob | relays |
+-------------+-------------+-----------+------------+--------+
| 0.2.9       |        33.3 |     37.76 |      32.53 |   1917 |
| 0.2.8       |        27.6 |     27.87 |      28.05 |   1582 |
| 0.2.7       |        10.2 |     10.47 |       9.12 |   1008 |
| 0.2.5       |         9.5 |      7.15 |       9.77 |   1219 |
| 0.2.6       |         8.6 |      3.02 |      10.91 |    492 |
| 0.3.0       |         5.8 |      8.99 |       5.06 |    174 |
| 0.2.4       |         4.7 |      4.70 |       4.54 |    787 |
+-------------+-------------+-----------+------------+--------+

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20170117/c6418a07/attachment.sig>