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

Re: When to tag was Re: Soliciting signatures for Subversion 1.1.4

From: Ben Reser <ben_at_reser.org>
Date: 2005-04-03 02:18:16 CEST

On Sat, Apr 02, 2005 at 03:37:34PM -0800, Justin Erenkrantz wrote:
> 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.

What's the confusion? I always announced on IRC when I was soliciting
testing what revision the release was cut from on the branch. The only
difference that would ever exist between the tag and the branch would be
the minor differences between the svn_version.h file.

> 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.

I have no problem with tossing the revision number if we toss the
tarball. But I don't think the tag should exist until we decide that it
is a good release.

> Our downstream packagers just need to be aware that a release isn't
> official until we send the announcement.

I think that's highly optomistic. Our repository is a communication
medium. Basically if you don't read dev you can't be sure what the
status of the tag is. When I've done announcements on the weekends
sometimes the announcement email hasn't been moderated through until

If you absolutely must have a tag then name it 1.1.4-test or something
like that. If the release is okay then mv it to 1.1.4, if it's trashed
then we just delete it and never post that tarball and start over with

But I really do believe that creating a tag says "this is a release."

Frankly, I've always wondered why we don't have a "tags" directory and a
"releases" directory. It seems cluttered to have release tags mixed
with unrelated tags that we might want to use. Plus having a releases
directory enhances the communication factor that the tag represents.

There can be a 1.1.4 in tags, but if we decide to never call it a
release for some reason it just wouldn't exist in releases.

Ben Reser <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
Received on Sun Apr 3 02:19:30 2005

This is an archived mail posted to the Subversion Dev mailing list.