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

Re: When to tag was Re: Soliciting signatures for Subversion 1.1.4

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2005-04-04 20:55:13 CEST

--On Monday, April 4, 2005 12:05 PM -0500 kfogel@collab.net wrote:

> IMHO it was -- thanks for posting.


> I think the big lesson we should draw here is that once a tarball has
> become publicly visible in any way at all -- by appearing in a
> downloads area, whatever -- we must consider it released. We don't
> have a choice about this. People will download it, people will base
> third-party releases on it, people will submit to Freshmeat, etc. It
> is *not* within our power to say "No, that wasn't a real release." We
> can shout it to the wind all we want, but it won't change the way
> people treat the tarball.

I agree that we have to say it's a release once we solicit signatures, but
what others do with it is never anything we can control. Someone could
take branches/1.1.x or trunk and call it a release, too.

> Therefore, I think it would be best to do the pre-release testing and
> signing processes privately, among the full committers, and *then* put
> the thing out where others can see it. If a problem is discovered
> after that, well, then we chuck that release number and make a new
> release with the next available number.

As I've mentioned before, I really disagree with this. I don't like
creating a star chamber where upon releases magically appear.

> This wold lose us a little bit in the "Do Everything Openly"
> department, but not in a major way, and I don't see any other way to
> do it. We want the release to be tested & signed; in order to do
> that, we have to test & sign it before we "release" it. We've learned
> that this verb "release" has a meaning we don't entirely control, so
> we have to be careful about what we make available and when.

I'd point out that other projects don't have this problem. I think it's a
matter of clearly defining what our release process is. -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 4 19:56:52 2005

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