Justin Erenkrantz wrote:
> --On Saturday, April 2, 2005 11:46 AM -0800 Ben Reser <ben@reser.org>
> wrote:
>> This is one of the reasons why I didn't want to tag 1.1.4 until we
>> approved the tarball. Tagging implies that it's ready to go...
>
> My concern is that once we send a public email to any list, that
> version is gone - hence, the tag should be laid down at that point. There
> should never be any confusion as to, say, what the 1.1.4
> release contains.
> I'm not comfortable sending anything to any list saying 'this is
> 1.1.4' (including to dev@svn soliciting signatures for approval)
> without having the /tags/1.1.4 created first. If there's a problem
> with the 1.1.4 tag during the signature process, then we would bump
> to 1.1.5 - not reuse 1.1.4.
> Our downstream packagers just need to be aware that a release isn't
> official until we send the announcement. -- justin
I agree with most of Justin's quoted comments - tagging just indicates a
release is in progress, not complete, and anyone who thinks otherwise is
being unrealistic.
HOWEVER, I do think that tarballs should NOT appear at
http://subversion.tigris.org/tarballs/ until after they are official.
I'm not entirely sure dev@svn is the right place to mention the existance of
the waiting-for-test tarballs, but I can't think of anywhere better.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 3 02:17:08 2005