"Bruce A. Mah" <bmah@acm.org> writes:
> More info on FreeBSD release engineering can be found at:
>
> http://www.freebsd.org/releng/
>
> Hope this is helpful.
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.
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.
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.
-Karl
---------------------------------------------------------------------
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:31:53 2005