I think it is a matter of confidence. The API module is solid.
If something outside of the API needs fixing, we can do so quickly without worrying about being handcuffed by BC. Since I am not the RM I would suggest a beta this week and 2.1 within 1 week after. Folks that are paying attention will play with the beta, others that are not can get 2.1. A 2.1 w/o a beta would be OK by me for the non-handcuffed reasons stated above. If at some later point, lots of 3rd parties end up relying on a stable Core module, we can worry about marking what is really public in Core vs. not. Gary On Mon, Sep 22, 2014 at 12:01 PM, Remko Popma <[email protected]> wrote: > Do we need to have a 2.1-beta release, or shall we just do a 2.1 release > (and follow up with 2.1.1 etc if issues are found)? > > When are we aiming to do this release? > > There are still ~10 open Jira tickets targetting 2.1. > Please take a look to see if that list is up to date. > -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
