On 9/4/13 3:44 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>HI, > >> Are you sure this assertion is true for branches under development (dev >>/ >> features or bugs). >As part of the current release process, the release is tagged and then >develop is merged into trunk, otherwise it would not be a true reflexion >of what we actually released. > >Can you see a better way of doing this? Makes sense. After we merge back in, can we set it back to 0 in the dev branch? IIRC, the git branching model somehow only changed the version in the release branch. I may be way off since I don't fully understand the issue. -Alex
