Sander Striker <firstname.lastname@example.org> writes:
> email@example.com wrote:
>> 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.
> It depends on where you put the tarball for testing. It definitely
> doesn't belong in subversion.tigris.org/tarballs/ during testing.
> If you put it in a place like: /testing/tarballs/ or something like
> that, the status of the tarball is a lot clearer.
We can also change the name of the tarball. The name doesn't have to
contain the version number, it doesn't even have to contain the word
"subversion". The tarball can later be renamed and any signatures
will remain valid.
>> 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.
> Heck no. We get into the smoke-filled-backroom-where-the-old-boys-decide
> what-is-a-release territory. Or at least the perception. Please keep it
> Also consider that when only allowing full-committers@ to participate,
> and thus to test, you are eliminating a useful group for feedback.
> People who have access to platforms we don't have access to, or maybe
> access to the same platform and actually have cycles to burn to do a
> testrun. Better to have dev@ figure out a release is a dud than to have
> the rest of the world come to that conclusion.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Apr 4 21:47:43 2005