[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-dev] onion v2 deprecation plan?
Hi nusenu,
I've just finished catching up with this thread, ticket changes,
and the IRC discussion overnight.
> On 28 Apr 2018, at 09:30, teor <teor2345@xxxxxxxxx> wrote:
>
> On 28 Apr 2018, at 05:56, nusenu <nusenu-lists@xxxxxxxxxx> wrote:
>
>>> And also we will be able to reduce the
>>> requirements for becoming an HSDir which will strengthen and make our
>>> network more robust.
>>>
>>> That said, I think we are unfortunately still far from deprecating v2
>>> onions:
>>
>>
>> thanks for listing all these relevant ticket IDs, I pasted your email into
>> trac and I made them child tickets of
>> https://trac.torproject.org/projects/tor/ticket/25955
>>
>> lets try to link all relevant tickets there
>
> Please don't, that confuses our workflow.
> A lot of these tickets are unrelated to v3 onion service features in Tor.
>
> If you want to link all these tickets somewhere, open another ticket.
I'm sorry, that was what you did.
But using the cyperpunks account made a few network team members
nervous. When we see accounts we don't know making sweeping
changes, we tend to revert them. That's what happened in this case.
You're welcome to use the cuperpunks account for any changes, but
please check with us next time before making large changes.
In this case, I'm not sure if we want a parent ticket, or a tag.
A tag might be more useful, because we use parent tickets for closely
coupled tasks. And when there are too many layers of parents, people
get confused.
T
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev