Re: [hibernate-dev] Why Hibernate 4.2.x should receive more updates

I simply do not consider Spring a valid reason to keep older Hibernate release families active. So to say its "not on the Spring team" and imply it is all Hibernate's problem is a bit misleading. Early in Spring/Hibernate integration they used to work with us to flesh out integration points. Of course they would have, they were looking for traction as a new project and wanted to ride on Hibernate's popularity. Since then, not only have they stopped reaching out to us, but in a few cases were I reached out to them and offered suggestions on how to do certain integrations I was ignored. So yes, in some ways it is on them. To me, if anything, a far more compelling reason would be JPA 2.0 (4.2) versus JPA 2.1 (4.3) support. However, you need to understand that this is an open source project. We simply do not have the man power that commercial offerings do. Us being able to keep up development and testing of all these "dead" branches is simply not feasible. On Sat, Apr 5, 2014 at 7:34 AM, Marc Schipperheyn <m.schipperheyn(a)gmail.com&gt;wrote: