New stable branch to replace releases branch
mbedward opened this issue · comments
Michael Bedward commented
As discussed on the mailing list, replace the "releases" archive branch with a "stable" branch where bug fixes and improvements relative to the most recently released version can be worked on.
Example workflow:
Last release was 1.3.1 so stable version will be 1.3-SNAPSHOT and master version will be 1.4-SNAPSHOT.
We do some bug fixes and improvements, commit them to stable (as
well as master if appropriate), then do a release by:
- set version to 1.3.2
- deploy artifacts to staging repo
- apply 1.3.2 tag to stable
- set version back to 1.3-SNAPSHOT
When we are ready to release 1.4.0 we do:
- merge master into stable
- set version to 1.4.0
- deploy
- apply 1.4.0 tag to stable
- set version to 1.4-SNAPSHOT on stable
- set version to 1.5-SNAPSHOT on master
Michael Bedward commented
Made changes and published blog post:
http://jai-tools.blogspot.com.au/2013/01/changes-to-source-repository-structure.html