Hello, maybe HSEARCH-534 could be considered: non-intrusive change, nasty bug too. What's the procedure? I suppose 1) edit "fix versions" to add the 3.2.1 2) merge the changeset in the branch or should we also open a new issue, or reopen the same one?
2010/7/19 Emmanuel Bernard <emman...@hibernate.org>: > Since 3.3 is not out yet (likely an end of summer target), I'm thinking on > releasing a maintenance version of the 3.2 series. > HSEARCH-540 is a pretty nasty bug (due to lack of Synchronization execution > ordering - see Re: [hibernate-dev] Exceptions thrown in a tx synchronization > are eaten by Steve on July 14th). > > Any other bug you think cannot wait and should be back-ported? > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
