> > > The author of the article seemed to want to make a release branch so that > whatever hits the trunk is essentially a snapshot of a release. I'm not > quite sure that is worth it if at the point there is a group of us > dedicated > to making a release and fixing things that are broken.
The point of the release branches are to prepare what is in the dev/trunk branch for release. That would include changing the build number, updating a change log, fixing docs, those types of minor changes that come with making a release. Even very minor bug changes can be done in a release branch. Once its ready to be shipped you push to dev/trunk which should trigger a Jenkins build which produces a new version of the product. If you continually make the small changes in dev/trunk then your continuously making new versions of the product, so the idea of the release branch is just to make those small changes and get it ready to 'go out the door'. Once it goes out the door you tag it and that's the EOL for the release branch. -omar
