[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Release policy question

From: Peter Samuelson <peter_at_p12n.org>
Date: 2006-02-03 06:58:53 CET

[Justin Erenkrantz]
> On 02 Feb 2006 12:25:35 -0600, kfogel@collab.net <kfogel@collab.net> wrote:
> > If release X is blessed by sufficient signers, and then later
> > discovered to have a security flaw, then those who installed release X
> > need to upgrade to a new, different release with its own sigs. That's
> > true no matter what the names of the releases are.
>
> There would be no way to know that release X and Y are different if
> they both report themselves as the same version.

I think the Evil Hacker scenario is a strawman. I don't see anyone
reusing a version number when the difference is something as
interesting as a security fix. We're talking about rerolling a tarball
because something procedural was done wrong. (That should be rare in
any case, since the procedures should be pretty much scripted.) Not
actual code changes.

Received on Fri Feb 3 06:59:26 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.