>So your formal releases are produced by manually running the release > >plugin? And if it fails, you manually do a rollback, > depending on the > >failure? > > Yes, we manually roll it back. It's not too bad with svn, but > a bit annoying I'll admit. We haven't tackled the release tools yet.
Ok cool. Myself and my collegues have been doing some thought in this area as well as to how to improve how releases are done using Maven. Once I formalize some of these thoughts I would like share them with the community to get some feedback. Perhaps later today if I can squeeze it in with my regular work ;-). > When we start to converge on a release, we cut a branch for > that release stream. That means that when we actually start > staging releases, the devs have moved on to the next release > which is another trunk/branch. This makes sense to me. In my mind, a release signifies an important milestone in the project and generally indicates the need to open a new branch so that you can reduce churn on that branch and continue regular more risky feature work. But this isn't the only work flow. Releases can be made off the trunk. Its the "continuous release" strategy that I think is throwing me for a bit of a loop. In this strategy many minor releases are made very often during the develop of a large major release of the product. This is a bit troublesome in the sense that your version number is constantly changing thus make SNAPSHOT versions less valuable. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
