Release Procedures: Tarball to Annoucement Timeframe

I guess sussman and I have been at a bit of corss purposes with respect
to testing and announcing the tarballs...

We require 3 signatures on each tarball. Sussman was trying to get them
as quick as possible with the idea that as soon as we hit that amount I
would announce.

Previous to rc4 it's pretty much always taken 24 hours to get that
testing and signatures done. RC4 happened faster than that so I
deliberatly waited.

Given that we have people all over the world contributing and providing
input I want to give everyone a chance to give feedback. Just because
we have 3 sigs on a .gz doesn't mean it was tested on a wide variety of
platforms. It's very possible most of us just tested on Linux.

I don't want to try and enforce that we test on certain platforms
because many platforms really only have one person available to test on
them. But I do want to give those people an opportunity to test.

So I think we should at a minimum wait 24 hours after the tarballs are
posted for testing to announce a release. This gives everyone time to
test the tarball. If we have 3 signatures on everything after 24 hours
then we cut the release.

Everyone okay with this?

-- 
Ben Reser <ben@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org