Is there a procedure for having 3.1.x issues moved to 3.2? Two tickets from the 3.1.2/3.1.3 days, in particular, that I've been watching for months still haven't been assigned. If there's anything I need to do to have them apply to the 3.2 branch (more than adding a comment such as cloning), please let me know.
Specifically they are: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1401 which outlines a fairly large problem with session.merge() while using versions. Test case included. http://opensource.atlassian.com/projects/hibernate/browse/HHH-1507 which points to a simple typo in hibernate-mapping-3.0.dtd, that forces us to patch every release. Thanks, Josh Moore The Openmicroscopy Environment All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
