I would say +1 for 1.7.0 in any case. And I would do in 2 steps: 1. release the trunk as it's today. Very stable and a huge amount of fixes and some important refactoring and add ons. Requires a 1.7.0 by itself and not only a 1.6.1. 2. upgrade to asm5 during the next 2 weeks and gather as many feedback as possible on 1.7.0. We can then just push a 1.8.0
Right after that, we can focus on 2.0 to support java ee 7 on a new branch. And stay with 1.x on release maintenance stage. We could at least maintain 1.7 and 1.! cause the code base is almost the same. Only all deps (openjpa, owb, xbean, etc) changed to support java 8. 2014-04-01 7:02 GMT+02:00 Romain Manni-Bucau <[email protected]>: > Id say +1...when well get asm5 (in progress see next lines). So just wait > few days and we upgrade once we support it to say consistent. > > About asm xbean vote is in progress, owb is using the snapshot but already > java5, openjpa has a patch for it and just wait it to be applied and our > code will be updated pretty quickly so just need time. > Le 1 avr. 2014 04:03, "David Blevins" <[email protected]> a écrit : > > > Romain had pinged me offline about the idea of upgrading our ASM > > dependencies to v5 so we could support Java 8 (code compiled in Java 8 > > can't be read by ASM v4 or earlier). > > > > This combined with the Mojarra and EclipseLink / Plume distribution seem > > like good features for a 1.7.0 > > > > We also have the quartz repackaging we did which are not quite "minor" > > patch changes. > > > > Any thoughts on updating the trunk version to 1.7? > > > > > > -David > > > > > -- Jean-Louis
