On Fri, Aug 19, 2011 at 4:01 PM, Kristian Rosenvold <[email protected]> wrote: > I had a small discussion with Tamas on IRC yesterday about this, and I did > come to realize that the proper way to do this is to do a regular release of > maven-archiver 2.4.2, then make a branch in svn for maven-jar-plugin 2.3.2. > On the branch, update to maven-archiver 2.4.2 and then release from the > branch. In that way the build never breaks and CI does not need any staging > dependencies. > > In retrospect I did the next-best thing, which was a temporary revert of the > upgrade on trunk. So I can procastinate/fear svn branches for a little > longer ;)
Whilst procrastination and fear are admirable attributes, doesn't creating a branch mean you miss all the good stuff of CI? And until you merge back to trunk your changes are not visible to others. I can't speak with any authority on what we do, but in my personal past I've had: * trunk - keep latest changes here but dont break the build * branches - something that is going to take a while to fix and/or is a work in progress so stuff may be not thought out well enough to live in trunk. But I dont see which one of these two scenarios your problem resides, i.e. you need a newer version of dependency that doesn't yet exist... Can't you stick with the snapshot until the release passes and then commit to the released version? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
