+1 We don't even need upfront maintenance branches for 1.7.1 vs 1.7.2 etc.
IF we need to ship a 1.7.1.1 version, then we can easily create such a branch from the 1.7.1 tag at any time anyway. Of course if it takes us longer to stabilize a version then we can roll a maintenance-1.7.1 branch even before we cut the release. But I'd only do this if we don't get this managed in other ways. Usually it is enough to just shout to the list that a release will be cut soon and people should abstain from committing experimental stuff but only fix important bugs on that branch. LieGrue, strub > On Wednesday, 28 January 2015, 21:35, Romain Manni-Bucau > <[email protected]> wrote: > > well while master = 2.x.x I wouldn't create it but yes (Tomcat model > basically is nice 1 maintaince branch by N-1 maintained version + > trunk for last one). > >
