>> I always create a "private" branch to make sure I don't destroy the trunk ;-) >> So, if something went wrong during "mvn release:prepare" it is only broken >> on my private branch. > > Ok. So this will be deleted when the vote has passed?
yes. usually on the same day :-) > >> >> > * you've created a "branches/1.2.7.1-branch" directory, where the pom >> > has a version of 1.2.7.1. What is this for? >> >> this is another private branch, which I once in a while create. >> Idea behind this is maintaining the 1.2.7 release. This was created >> by accident. Usually this is not needed on the plugins, but we had already >> a 1.x.y.1 release in the past... where something was really bad, but it >> wasn't >> worth to do a new 1.x.y+1 release. Does that make sense ? > > Why not wait until it is needed before creating it? Less work, and less > confusion. When a critical patch is needed, can't the release tag be copied > into the branches dir as a base for the new work? yes. I made a mistake. a) I usually use the TAG b) I usually do it on the plugins only, when needed. -M > > Cheers, Simon >> > > -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
