Agreed - as this is in progress (thanks Mark!) I think we should wait it out - if it passes, that's great. If not, we can discuss what plan 'B' might be.
Jon On Mon, Apr 20, 2015 at 7:15 PM, Jean-Louis Monteiro < [email protected]> wrote: > +! > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > On Mon, Apr 20, 2015 at 11:13 AM, Andy Gumbrecht <[email protected] > > > wrote: > > > If the vote passes then all is good, I guess this discussion is a ' just > in > > case' track. > > > > http://www.tomitribe.com - @AndyGeeDe - On a small screen device. > > On 20 Apr 2015 20:08, "Mark Struberg" <[email protected]> wrote: > > > > > openjpa VOTE is on the way… > > > > > > LieGrue, > > > strub > > > > > > > > > > Am 20.04.2015 um 18:11 schrieb Andy Gumbrecht < > > [email protected] > > > >: > > > > > > > > Sorry guys, still mobile. Defo + 1 to release asap. Even the noise > will > > > do > > > > us good, and the 1.7.3 can follow just as quickly. > > > > > > > > http://www.tomitribe.com - @AndyGeeDe - On a small screen device. > > > > On 20 Apr 2015 17:41, "Jean-Louis Monteiro" < > [email protected]> > > > > wrote: > > > > > > > >> I'd say go without OpenJPA by using the our internal fork and do a > > 1.7.3 > > > >> when OpenJPA is available. > > > >> > > > >> -- > > > >> Jean-Louis Monteiro > > > >> http://twitter.com/jlouismonteiro > > > >> http://www.tomitribe.com > > > >> > > > >> On Mon, Apr 20, 2015 at 7:32 AM, Jonathan Gallimore < > > > >> [email protected]> wrote: > > > >> > > > >>> Hi > > > >>> > > > >>> I would still like to be release manager for TomEE 1.7.2. I don't > > have > > > a > > > >>> strong preference on going ahead straight away or waiting for the > > > OpenJPA > > > >>> release. I'm equally happy to do a 1.7.3 release shortly after > 1.7.2, > > > no > > > >>> problem. Romain has quite a strong view that the OpenJPA release > > really > > > >> is > > > >>> needed for this release. > > > >>> > > > >>> For reference, here's the original discussion: > > > >>> > > > >>> > > > > http://tomee-openejb.979440.n4.nabble.com/openjpa-patches-td4674131.html > > > >>> > > > >>> And the two JIRA issues: > > > >>> > > > >>> https://issues.apache.org/jira/browse/OPENJPA-2573 > > > >>> https://issues.apache.org/jira/browse/OPENJPA-2511 > > > >>> > > > >>> If anyone else has a view, please feel free to give it here, and > then > > > >> maybe > > > >>> we can decide together to push forward, find another way to resolve > > > these > > > >>> issues, or roll this release with out these fixes, and roll another > > one > > > >>> once they are available. > > > >>> > > > >>> Jon > > > >>> > > > >>> On Mon, Apr 20, 2015 at 3:08 PM, Jean-Louis Monteiro < > > > >>> [email protected]> wrote: > > > >>> > > > >>>> Hi guys, > > > >>>> > > > >>>> Let's have the discussion in a different email. > > > >>>> Jon did the first roll for 1.7.2 but it's been canceled because > of a > > > >> big > > > >>>> issue. > > > >>>> > > > >>>> It's been a while and probably time to start again. > > > >>>> There is an openjpa bug pending but I do agree with Andy, we > should > > do > > > >>>> anyway and release a 1.7.3 later. > > > >>>> > > > >>>> For years, we have been suffering of long release cycles not > because > > > >> PMCs > > > >>>> are blocking but because we are always waiting for x y z to be > fixed > > > >> (x, > > > >>> y, > > > >>>> z being bugfixes, dep upgrade or whatever). > > > >>>> > > > >>>> We have Jon still happy to do the release 1.7.2 and Andy also > happy > > to > > > >> do > > > >>>> it. > > > >>>> As users are expecting a TomEE 2 for a while probably Andy you > could > > > >>> focus > > > >>>> on doing a TomEE 2.x milestone? > > > >>>> Needs another thread to discuss, but that's an idea. > > > >>>> Another one would be to have you do the 1.7.3 when openjpa is > fixed. > > > >>>> > > > >>>> -- > > > >>>> Jean-Louis Monteiro > > > >>>> http://twitter.com/jlouismonteiro > > > >>>> http://www.tomitribe.com > > > >>>> > > > >>> > > > >>> > > > >>> > > > >>> -- > > > >>> Jonathan Gallimore > > > >>> http://twitter.com/jongallimore > > > >>> http://www.tomitribe.com > > > >>> > > > >> > > > > > > > > > -- Jonathan Gallimore http://twitter.com/jongallimore http://www.tomitribe.com
