well, the issue i saw was if we look to current trunk we should almost backport all fixes
- Romain 2012/6/4 Jean-Louis MONTEIRO <[email protected]> > Having frequent releases maintenance on 1.0.x and 4.0.x is definitely > required for end users. > > David's rule seems a bit difficult, but let's try it. We will not merge > everything but we want to get fixes in, so a JIRA must be created. In that > context, I think an SVN hook would be great to ensure relevant release > notes. > > Thanks David for the job. > > JLouis > > > 2012/6/4 Romain Manni-Bucau <[email protected]> > > > Ok so finally we agree, you are just in BranchType.EAGER were i'm in > > BranchType.LAZY ;) > > > > - Ronain > > Le 4 juin 2012 04:10, "David Blevins" <[email protected]> a écrit > : > > > > > On Jun 3, 2012, at 5:53 PM, Romain Manni-Bucau wrote: > > > > > > > Let say we can release often, releasing from trunk should be easy. > > > > > > > > Today that's hard because we dont do it (tomcat, cxf, cassandra etc) > > are > > > > good examples > > > > > > It isn't really about what is easy or hard -- though that is a factor. > > > > > > Obviously when we change things like adding JAX-RS to Web Profile, > that's > > > more a 1.1.0 change. New consoles and other new features are great > too, > > > but are also a bit bigger. As well we don't have any say in when new > > > features are finished -- they're done when they're done. > > > > > > If people want just a couple fixes and don't want to wait, I'm happy to > > > give it to them. > > > > > > > > > -David > > > > > > > > >
