This content has been marked as final.
Show 1 reply
-
1. Re: Micro-release strategy issues
lfryc Apr 24, 2012 11:35 AM (in response to lfryc)As we have discussed, the origianl Git Flow didn't run into this problem, since it was designed for short-running hotfix releases instead of long-running development on branch divergred from tag.
----
To fix this, I would suggest following strategy in next minor release:
- opening
- open the develop/4.2.1.Final branch from 4.2.1.CR1 tag
- switch the version to 4.2.1.Final-SNAPSHOT (to distinguish bits in continuous integration)
- development
- sprint on develop/4.2.1.Final branch
- release
- open the release/4.2.1.Final branch
- switch version to 4.2.1.Final
- integrate develop/4.2.1.Final to develop
- continue with release as usual
- continue with develop (having changes from develop/4.2.1.Final)
- could be even parallel to release
- opening