[jboss-dev-forums] [Design of JBoss Build System] - Re: New Release Process

[scott.stark@jboss.org]

For any reasonably stable project I already expect there to be a branch. The issue with incrementing either the branch or trunk to the next version exists for either strategy as both end up with a codebase that does not match the tag as soon as another change is made. The http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html docs say that existing poms are updated though:

Bump the version in the POMs to a new value y-SNAPSHOT (these values will also be prompted for)

If that is the case whether or not a branch is used is just a function of the project maturity/policy. If there is not already a branch its not helping much to create one.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032136#4032136

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032136