I just wanted to get the lay of the land regarding peoples method of 
committing release candidate changes in Git.

Using either automake or cmake, the release candidate is set in either 
configure.ac or CMakeList.txt, and thus used in RPM version and Git tag 
when building.

When using Maven, it gets the following commits each time I release a new 
version (stable or RC).
    [maven-release-plugin] prepare for next development iteration
    [maven-release-plugin] prepare release v1.0.1


>From some of my peers I have seen some frustration in having to bump up the 
version for each release candidate manually. Also specially when there is 
no source code change, but a change in a static library and we need a new 
release of all projects that uses it.

change release candidate
commit change
build new release candidate
fixes..
fixes.....
change release candidate
commit change
build new release candidate
change release candidate to release
commit change
build new release

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to