Hi,
Just off the top of my head, but didn't want to forget about it. Now
that we stage, it seems a bit strange to tag the final release before
pushing it up. Does the below seem like a sensible amendment to the
previously discussed process?
release:prepare:
- branch code
- checkout branch in target
- update poms to release version on branch, commit
- update poms to next dev version on trunk, commit
release:stage:
- done from branch, deploy to staging. Operates mostly like
release:perform, but skip the 'tag' bit.
release:perform:
- tag, move from staging to production
The release plugin should still be able to work in the simpler mode
where it all happens on trunk, and I guess if the release needs to be
done again the new rollback stuff can be used.
Thoughts?
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
