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

Re: Release, bindings (Was: svn commit: r12731 - trunk/notes)

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2005-01-14 20:57:23 CET

--On Friday, January 14, 2005 1:36 PM -0600 kfogel@collab.net wrote:

> Are you saying that it would be difficult to build a source -beta
> tarball followed by a true release tarball, such that the only
> difference between them is the version label? (That's surprising, if
> so.)

I believe there should be no differences whatsoever between what is
approved for release and what is actually released. If you make any
changes to the release file, something could go wrong. I think the release
in its final state should be approved as-is by the committers.

> That's an independent proposal, I think. If we want to have 3 or 4
> developers test it, we can do that as easily with beta tarballs as
> with true-but-slightly-secret tarballs. The difference is that we
> can't let the latter kind of tarball out where other people could test
> it too. That seems a pretty large disadvantage...

No, I think the issue is to introduce it as a forcing factor: if three
committers approve the release, we can say that we put forth due diligence.
At this point, we don't have such safeguards. -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 14 21:00:35 2005

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.