> Digging up the specific details is where most the work is. David, the issue is to build release notes? I guess most of the work (at least crossing fingers) is attached to a fully filled and documented Jira, isn't it? ;-)
Anyway, I can try to extract kinda release notes and go through all Jira tomorrow to check whereas I can understand them. I pretty sure we have enough things and so many new features to emphasis on a new "major" version (ok, that's still a minor, but you know). JLouis 2012/9/19 David Blevins <[email protected]> > > On Sep 19, 2012, at 12:46 PM, David Blevins wrote: > > > > > On Sep 19, 2012, at 8:45 AM, Jean-Louis MONTEIRO wrote: > > > >> Hello guys, > >> > >> Was looking to release notes and all the work we did since last release > >> 1.0.0. > >> I was wondering if we could jump to a 1.5.0? > >> > >> IMHO, the gap between both is really big (large improvements, > classloading > >> changes, ear support, lot of bugfixes, and lot of new features) and > require > >> also a gap in versioning. > >> > >> Moreover, I think it's great for the community and for external users to > >> reflect all those changes in the version number. > >> > >> Thoughts? > >> Anyone against the idea? > > > > I'm fine with the idea. > > Let me rephrase and add some caveats :) I'm fine with the idea provided > we can draft up an exciting enough announcement. Digging up the specific > details is where most the work is. > > If we can get something impressive looking by say Friday or Saturday, I'm > +1. If it turns into an idea with no volunteer, then -0. > > > -David > >
