On 12/11/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote:
<snip/>
And I too would like another way how we move forward to a release (at
least if my understanding matches with what you mean).
Is it like this?:
*) create a version tag in svn - the final tag - in this case "vfs-1.0"
<snap/>
No, tag remains VFS_1_0_RC9. But version numbers in
{project,build,pom}.xml etc. get set to 1.0 (not 1.0-RC9). If you
want, here is a recent example (long URL, may be fragmented):
http://svn.apache.org/repos/asf/jakarta/commons/proper/scxml/tags/SCXML_0_6_RC1/
The advantage is you can copy the exact binaries that were voted on to
the Jakarta dist/ space (no rebuild, so actually less work for the RM
as well). You can also simply copy this tag to the final VFS_1_0 tag
if the vote passes.
*) switch local version to this tag (or checkout at a different place)
<snip/>
Yes :-)
*) remove SNAPSHOT from various build files
<snap/>
Not needed, see above.
*) create distribution - creates artifact with correct final version
*) after the vote has passed we simply can copy these version to their
final destination
<snip/>
Indeed.
-Rahul
Ciao,
Mario
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
