+1 if there is a clear statement of what is there and what is not (keep in mind we'll not run in a container expecting a JPA 2.1 implementation but we would be detected as such cause of the API which is - fakely - implemented). A page on the website is far enough but needs to be there for the m1 (can be done in parallel of the vote but don't want it to be missed). Shouldn't be too hard since we throw UnsupportedOperationException with a JPA 2.1 message IIRC for most of these cases (excepted DDL properties I think).
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-11-08 8:58 GMT+01:00 Francesco Chicchiriccò <[email protected]>: > On 08/11/2016 08:56, Mark Struberg wrote: > >> hi folks! >> >> I'd love to run a release build for our first 3.0.0 milestone today or >> tomorrow. >> Any objections? >> Trying to close a few resolved JIRA tickets, but rest should be ok, wdyt? >> > > +1 nice move! > > After that, do you think it would be possible to start thinking about > 2.4.2? I see there are already several improvements over 2.4.1 available. > > Regards. > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Member at The Apache Software Foundation > Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail > http://home.apache.org/~ilgrosso/ > >
