> On 18 Jan 2017, at 09:22, nusenu wrote:
>
>> == 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 retro
> == 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
>sup
On Mon, Jan 16, 2017 at 4:12 AM, grarpamp wrote:
> You may encounter special justification to
> extend support for last branch that still supports
> pre-prop224 onions. There is a *lot* of code / community
> built on those. Darknet fora have mentioned possible
> maintenance forks as such if need b
You may encounter special justification to
extend support for last branch that still supports
pre-prop224 onions. There is a *lot* of code / community
built on those. Darknet fora have mentioned possible
maintenance forks as such if need be.
___
tor-dev m
On Fri, Jan 13, 2017 at 1:54 PM, Ian Goldberg wrote:
> On Fri, Jan 13, 2017 at 09:29:25AM -0500, Nick Mathewson wrote:
>> Hi, all!
>>
>> This is a draft for a tor long-term support policy for the program
>> "tor". Please let me know what you think. It's based on earlier work
>> and surveys, but i
On Fri, Jan 13, 2017 at 09:29:25AM -0500, Nick Mathewson wrote:
> Hi, all!
>
> This is a draft for a tor long-term support policy for the program
> "tor". Please let me know what you think. It's based on earlier work
> and surveys, but it isn't final till we say it is, and it needs more
> comment
Hi, all!
This is a draft for a tor long-term support policy for the program
"tor". Please let me know what you think. It's based on earlier work
and surveys, but it isn't final till we say it is, and it needs more
commentary.
Please keep in mind that dropping support for any old release is an
in
