neil hart wrote:
When we use the release plugin it works well by:
- Changing our x.x-SNAPSHOT to x.x
- Checks in and tags our code with the x.x version number
- Changes x.x to x.x+1.
We would like to have some way of starting a branch from the tagged code
and
have it change our x.x to x.x.1-SNAPSHOT so we can release using the
branched version number. Does something like this exist? Should we do the
release step differently? Is there a better way of handling this?
We are currently trying to simplify and automate our deployment
procedures, and are interested in some elaboration.
I suggest the following procedure:
Assume trunk is x.y-SNAPSHOT and that Xstream's versioning scheme [1] is
used.
1. Create a new branch named release-x.y from trunk and set version to
x.y in the pom of this new branch.
2. Change trunk version to x.y+1-SNAPSHOT
(Trunk is now ready for further development and you have a
release-branch to create releases from.)
3. Create a tag x.y.z from release-x.y branch and deploy artifact
_Questions_:
a. Is this the procedure you want?
b. Is this procedure supported by the release-plugin?
c. Is this best practice? If not, what's wrong or should be changed?
[1] http://xstream.codehaus.org/versioning.html
--
Regards
Erik Drolshammer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
