I see a major difference though, because the release branch is a branch to
be released, it can add the build number without affected the normal git
workflow, the release branch is based on the develop branch (think extends),
they don't need to be equals in everything, that's the goal of doing a
release branch, make the release into, so, it means as well adding the build
number.

-Fred

-----Message d'origine-----
De : Justin Mclean [mailto:jus...@classsoftware.com] 
Envoyé : jeudi 5 septembre 2013 01:48
À : dev@flex.apache.org
Objet : Re: Nighly builds and releases

Hi,

> Following nvie.com/posts/a-successful-git-branching-model/ the develop 
> branch is never merged to the trunk but the release branch yes.

Yep that right, I've not had my coffee yet :-) 

Same issue basically as the release branch is branched from develop, worked
on, tagged, released and then the release branch is merged back into both
develop and trunk.

Justin

Reply via email to