Release branches act as a buffer between feature development (develop)
and public releases (master).
Whenever you merge something into master, you should tag the commit for
reference
git tag -a tomee-1.7.2 -m "TomEE 1.7.2 Release" master
git push --tags
On 17/10/2014 16:46, Romain Manni-Bucau wrote:
sorry I'm surely slow today but it if can avoid me 1h ;): so what's
different with tags? ie when do you go to master without having a
release?
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2014-10-17 16:41 GMT+02:00 Andy Gumbrecht <agumbre...@tomitribe.com>:
Not quite, the /release /branch takes place 'whenever' - This means it would
be 'nice' to create it from a stable /develop/, but is NOT required (this is
the big +1 for me).
The /release /branch is where the release is polished and prepared and all
the tests must 'eventually' pass - work can continue in /develop/ (another
big +1) - everyone can help make the /release /stable.
When the /release /branch is ready then it is merged to /master /*and
*/develop /(if there were changes in the /release /then they also need to
get merged back to /develop/)
The /master /branch only ever contains stable production ready code.
Andy.
On 17/10/2014 15:54, Daniel Kasmeroglu wrote:
Regarding the creation of a release branch I assume that creating the
branch from 'develop' implies that all available tests and quality
criteries must be matched before the actual branching takes place.
Am I right on this ?
Best regards
Daniel Kasmeroglu
--
Andy Gumbrecht
https://twitter.com/AndyGeeDe
http://www.tomitribe.com
--
Andy Gumbrecht
https://twitter.com/AndyGeeDe
http://www.tomitribe.com
