I really don’t care how we call it. Though our versions don’t match the spec versions anymore anyway. And it’s essentially a new major release. So I’d rather follow semantic versioning and move to 3.0.
To express it in Apache terms: I’d be +0 for 2.5.0 and +0.5 for 3.0.0 But I have no strong feelings about it either way. LieGrue, strub > Am 18.08.2016 um 11:13 schrieb Romain Manni-Bucau <rmannibu...@gmail.com>: > > 2016-08-18 8:45 GMT+02:00 Mark Struberg <strub...@yahoo.de.invalid>: > >> I finally went ahead and will start with the tasks >> >> I just created a 3.0.0 version in Jira. >> >> > Mainly curiosity since I don't care much of digits but why not 2.5? > > >> I suggest we copy the current trunk to branches/2.4.x and continue >> maintaining all JPA-2.0 stuff over there >> >> > +1 > > >> Will create JIRA tickets for all the tasks we need to do. >> >> Anyone is welcome to help! >> >> txs and LieGrue, >> stru >> >> >>> Am 04.05.2016 um 08:26 schrieb Francesco Chicchiriccò < >> ilgro...@apache.org>: >>> >>> 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/ >>> >>> >> >>
