Some questions for discussion:
Instead of creating a tag directly off the trunk, maybe we should first create a branch
for the release and increment the trunk to the next version? Then the tag would be
created from the branch, and if problems are found in the tag, the tag is deleted, and the
bugs are fixed in the branch. The maven release plugin is not currently set up to do
branches, but this is something that could probably be added pretty easily.
Instead of having QA test the actual release, maybe they can test the release candidate
version, and if everything is fine, then we just rename the release candidate and do some
verification that the bits are the same.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032119#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...