Hello Jody, yes this branch was intended to replace trunk when a bit more advanced. There are still things we can take from Pinaki work but some API changed and needs a migration.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-06-17 17:35 GMT+02:00 Jody Grassel <[email protected]>: > Hey there, I noticed the openjpa/branches/openjpa_jpa-2.1 branch today. > I'm assuming it's not yet a complete implementation of the 2.1 spec yet > (changesets after the branch create look limited to stored procedure > support), so I have to ask if openjpa/branches is the correct place for the > project (which is typically where users go to for serviceable rather than > incubating components). In the past, experimentation (non trunk > development was the providence of the openjpa/sandboxes branch - which > already contains a 21 project that Pinaki opened in 2013. >
