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

[teor]

> 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/

T


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20180113/1575e78f/attachment.html>