Unless we actually change the API I see no reason to call it 3.0 even if we upgrade the minimum JDK. The release notes have made it clear that the change is coming.
Ralph > On May 3, 2015, at 11:06 AM, Gary Gregory <[email protected]> wrote: > > If I had the time to do releases, I would propose: > > - Release 2.3 ASAP. Perhaps as soon as the Jenkins issue is resolved or a > workaround documented. We have plenty of fixes for a 2.3. > > - Depend on Java 7 and release the same code as 2.3. Personally, I would call > this 3.0 to make it clear the platform change is important (see below) This > leave room in the 2.3.x line for Java 6 releases if needed. > > Then release a 3.0.1 that actually takes advantage of: try-with-resources, > String switch, diamond notation. any Java 7-only APIs (NIO 2.0), updated > dependencies, file change notification for configuration updates, and so on. > > The Java 7 based release could also be called 2.4 for the more conservative. > > Thoughts? > Gary > > -- > E-Mail: [email protected] <mailto:[email protected]> | > [email protected] <mailto:[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 <http://garygregory.wordpress.com/> > Home: http://garygregory.com/ <http://garygregory.com/> > Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
