Jukka Zitting wrote: > Hi, > > 2009/8/26 Thilo Goetz <twgo...@gmx.de>: > >> So far, we've always followed that model. I still prefer it, >> not least because it forces you to concentrate on the upcoming >> release. >> > > OK, sounds good. > > You may want to keep this alternative in mind though for future, often > especially in bigger projects it may become troublesome to enforce a > project-wide code freeze as contributors and committers from diverse > backgrounds may have different agendas and schedules. A release branch > is an easy way to limit the impact of the code freeze. > Thanks, Jukka. I actually thought about doing it the other way, but wanted to avoid "double updates" for bug fixes in both the main and release branches. But maybe that's not too hard to do with modern SVN tooling...
Also, I wonder about about sometime in the future integrating the maven "release" plugin. We currently don't use it - it used to have a show-stopper defect for us since we use Eclipse workspaces - resulting in a "flat" hierarchy for our projects, instead of the nested hierarchy in maven projects. I see that defect http://jira.codehaus.org/browse/MRELEASE-261 may have fixed this now, so we may try again... although I realize there may be additional things we will have to alter to get this to work... -Marshall > BR, > > Jukka Zitting > > >
