Yep, sounds like the right plan of attack. Just for posterity and the potential for a 2.1 release down the road, maybe you want to cut a "sandbox" branch for the 2.1 development? And, then declare trunk as 2.2?
-- Kevin On Mon, Jul 24, 2017 at 1:16 PM, Romain Manni-Bucau <[email protected]> wrote: > +1 > > Le 24 juil. 2017 20:01, "Francesco Chicchiriccò" <[email protected]> a > écrit : > > > Mark Struberg <[email protected]> wrote: > > > Hi! > > > > > > The JPA-2.2 spec is out and and only contains minor changes over 2.1. > > > I already noted in the board report that it might make sense to > directly > > move to JPA-2.2 in trunk. > > > Because finishing an obsoleve version is probably not worth it. > > > We imo better focus on getting 2.2 done. > > > > > > Wdyt? > > > > +1, go ahead. > > Regards. > > >
