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

I'm replying in general, with topic headings in lieu of quoted text.

1) "When to tag"

I think it is correct that "tags/1.1.5" _must_ be identical code to
"subversion-1.1.5.tar.bz2".
Thus, as soon as a tarball with that name is created, the relevant tag
should be present.

In order to prevent people jumping the gun, how about naming prerelease
tarballs something like "subversion-1.1.x-r18000.tar.bz2"? The content is
exactly specified, and it is clear it is not a "normal" tarball. When
approved, the tarball simply gets renamed.

Regarding the issues of svn_version.h - how about a "freeze-version" script,
which performs the necessary transformation in a publicly defined way.

2) "Use of dev@subversion"

I don't think there is any need to carry out releases in secret
(svn-full-committers), but I am concerned that dev@subversion has a somewhat
different "flavour" to dev@httpd - I think we have a higher populations of
users on our dev list.

Therefore, I would like to propose that we continue using dev@subversion,
but carefully never mention an exact version number in a pre-release
announcement. i.e. instead of "1.1.5", say "the next 1.1.x", or similar.

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 13:28:12 2005