[tor-dev] [tor-relays] Marker branch for current tor release(s)

[teor]

> On 24 Jan 2018, at 20:02, teor <teor2345 at gmail.com> wrote:
> 
> (I dropped tor-relays, we can tell them when we reach a conclusion.)
> 
> Hi Nick,
> 
> Can we maintain an "alpha" branch with the latest Tor alpha,
> and a "stable" branch with the latest Tor stable?

I was just told about the previous thread and ticket for this feature:
https://lists.torproject.org/pipermail/tor-dev/2015-March/008582.html
https://trac.torproject.org/projects/tor/ticket/14997

weasel wrote:
> Running the current alpha should always be a deliberate decision.
> If you can't be bothered to change your sources.list once or twice
> a year, then you probably should be running stable.

Has the reasoning changed?

> It would help some relay operators.
> 
> And it would also help us get more alpha testing:
> https://trac.torproject.org/projects/tor/ticket/24994#comment:4
> 
> Because the experimental deb repos on this page are tied to a
> particular release of Tor:
> https://www.torproject.org/docs/debian.html.en
> 
>> On 13 Jan 2018, at 09:06, teor <teor2345 at gmail.com> wrote:
>> 
>> 
>>> On 13 Jan 2018, at 08:07, Andreas Krey <a.krey at gmx.de> wrote:
>>> 
>>> (Earlier reply has somehow vanished...)
>>> 
>>>> On Mon, 08 Jan 2018 00:49:16 +0000, teor wrote:
>>>> ...
>>>> When there are multiple supported tor versions, which one should be stable?
>>>> At the moment, we support 0.2.5 and 0.2.9 as long-term support, and 0.3.0 and
>>>> 0.3.1 as regular releases.
>>> 
>>> The newest/highest, probably. Essentially the one also
>>> proclaimed as stable on the source download page.
>>> 
>>>> Should stable be 0.3.1 (and change to 0.3.2 next week)?
>>> 
>>> Yes.
>>> 
>>>> Do you want a long-term support branch as well?
>>> 
>>> No. I just need one version to build a relay.
>>> 
>>> ...
>>>> If you want something that's easier to scrape, and signed, check for
>>>> new source releases at:
>>> 
>>> Scraping would be a fallback.
>>> 
>>> ...
>>>> $ curl http://197.231.221.211:9030/tor/status-vote/current/consensus-microdesc | grep server-versions | tr "," "\n" | tail -1
>>>> 0.3.2.8-rc
>>> 
>>> Basically current would be the highest non-rc on the list,
>>> and alpha would be the -rc (or current if no -rc present).
>> 
>> We also tag releases with "alpha", so these should be included
>> in the alpha branch as well.
>> 
>> Is there any reason you can't use the source tarballs for this?
>> They are signed, unlike git branches.
>> 
>> https://dist.torproject.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20180124/78ab8ad4/attachment.html>