Hi Mark,
I am the latest coming at the party, so please my replies embedded below
with caution (and patience, in case..).
Thanks for moving this topic forward.
Regards.
On 04/05/2016 07:45, Mark Struberg wrote:
Hi!
We have a jpa-2.1 branch since quite some time. Romain started to implement
some features and I EE7 is already pretty mature. How do we like to proceed
with this work?
1.)
a.) leave 2.4.x as trunk and merge over the features to the jpa-2.1 branch?
b.) move the current trunk to maintenance-2.4.x (and actively maintain it) and
merge Romain's work to the trunk?
I see (b) as more appropriate: 2.4.0 was released about an year ago,
2.4.1 has been around for a while, and maybe we'll have the chance for
2.4.2 soon.
2.) What version should the jpa-2.1 OpenJPA release finally become?
3.0?
Looks good!
Do we like to do upfront -m1, -m2 etc releases?
Personally, I think this is a good strategy to give some time to other
using OpenJPA to adapt to the new features.
+1
I try to do a signature check on the jpa-2.1 jar in geronimo-specs with the
official jpa-api jar and improve the docs. Imo this should be our fist step.
Anyone up for some pair programming or review (ofc not now but at some evening)?
Unfortunately, I don't think I can be available for this, even though it
would be a very interesting opportunity for me to learn - maybe less for
being helpful to you :-)
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC,
Olingo PMC, CXF Committer, OpenJPA Committer
http://home.apache.org/~ilgrosso/
