I’d say we keep the jpa-2.1 work in the branch for now and use trunk for maintenance for now. If we feel that we are close to getting JPA-2.1 done then we can switch branches pretty easily.
I’d rather like to avoid tons of merges to different branches. That doesn’t scale well with SVN ;) LieGrue, strub > Am 01.06.2015 um 17:43 schrieb Kevin Sutter <[email protected]>: > > Hi Romain, > Thanks for kickstarting the JPA 2.1 activity! This may be a rough ride > until we get some of the bumps figured out... For example, I wasn't aware > of a specific branch for the JPA 2.1 work activity. I thought we were > going to do JPA 2.1 in trunk now that we cut the 2.4 release... Unless I > missed something in the discussion. > > As far as missing a few things... Wouldn't surprise me. The JPA 2.1 work > kind of stalled after the initial work was defined. Here are the tasks > that I originally outlined based on the updates in the spec: > http://openjpa.apache.org/jpa-2.1-tasks.html > > Also, note that Pinaki had done some initial work in his sandbox. The > sandbox is still there, but it's based off an old version of trunk, so I'm > not sure how difficult the merge will be: > https://svn.apache.org/repos/asf/openjpa/sandboxes/21 > > Hope this helps, > Kevin > > On Sun, May 31, 2015 at 8:21 PM, Romain Manni-Bucau <[email protected]> > wrote: > >> Hi guys, >> >> created https://issues.apache.org/jira/browse/OPENJPA-2592 >> >> wonder what's the status of 21 branch, seen impl was started but seems to >> miss few things (since my test doesn't pass) >> >> any inputs? >> >> Romain Manni-Bucau >> @rmannibucau <https://twitter.com/rmannibucau> | Blog >> <http://rmannibucau.wordpress.com> | Github < >> https://github.com/rmannibucau> | >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber >> <http://www.tomitribe.com> >>
