Closing in preparation for releasing 4.3.6.

Fixed in 4.3 branch.

I only see commits for 4.3, so I removed 5.0.0 from Fix Versions.

Please open a new Jira issue for 5.0.0 if you intend to fix it for that version.

Thanks,
Gail

Sorry I have overreacted a bit. I do see red when unnecessary red tape happens these days but here it's a bit complicated.

This issue should not have been marked resolved in the first place as it is still pending a push to master. Admittedly if the 4.2 backport resolution takes time (due to the perf team), it is probably easier to create a separate issue for it or reopen this one to add the version and close it again.

The release has been delayed until Wednesday, so that gives us some time to get this fixed on the appropriate branches. Is it enough time?

I was under the impression that when an issue was Closed, that no more work would be commited for that issue. If any more work is required (including in a different branch), then it would be done in using a new Jira issue. I thought that was what we had agreed on. If not, this should be brought up on hibernate-dev mailing list.

I don't see a problem with using a new Jira issue if something ends up getting backported later to an earlier branch. As long as the Jira issues are linked, it's not difficult to follow.