Re: [tor-talk] announcing releases

[tagnaq <tagnaq@xxxxxxxxx>]

On 04/17/2011 06:23 AM, Roger Dingledine wrote:
> The trouble is the definition of 'available for download'.
> 
> I can announce the release when the tarball is made, but then most
> users (including I think you?) will find that it is not yet available
> for download by their definition.

From my point of view it would be better to announce* a release at the
time when the tarball is available opposed to the point in time when all
packages and bundles are available. Mentioning the fact that packages
and bundles will follow (in the next few days?) should be enough?

This way the window of exposure in case of security fixes is smaller and
people can prepare/plan for an upgrade or stop the Tor process till they
completed the upgrade if it should contain critical vulnerabilities.
(Assuming the bad guys know about security related fixes as soon as the
change hits the git repo.)

I think this topic boils down to the question:
'Is it better to announce a release shortly before or after it is
available?'
I think it is better to know about a release shortly before it is
available, also if this means that user need to 'poll' the download
page/repos to see if the announced release is indeed available.

best regards,
tagnaq

(*) The method of announcements (email, twitter, ...) is not important
as long as it is defined.
_______________________________________________
tor-talk mailing list
tor-talk@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk