Tags
Authors
Jira Automations
I recently enabled a number of Jira Automations which focus on closing issues which are considered stale. An issue is considered stale when
-
A test case was requested more than 30 days ago, but one was not provided. This rule considers both Pull Requests and attachments, though not "test cases" defined in description or comments.
-
Additional information for an incomplete report was requested more than 30 days ago, but no reponse was provided.
As with any attempt at automation, there will be cases which do not fit nicely into the automation rules - both false positives and false negatives. If you feel one of these issues was incorrectly closed, re-open it. Which assumes that there is a test or response of course :)
Today, we published a new maintenance release of Hibernate ORM 6.2: 6.2.6.Final.
Today, we published a new maintenance release of Hibernate ORM 6.2: 6.2.5.Final.
Today, we published a new maintenance release of Hibernate ORM 6.2: 6.2.4.Final.
Today, we published a new maintenance release of Hibernate ORM 6.2: 6.2.3.Final.
Today, we published a new maintenance release of Hibernate ORM 6.2: 6.2.2.Final.
Today, we published a new maintenance release of Hibernate ORM 6.2: 6.2.1.Final.
Hibernate 6.2 Final
Hibernate ORM 6.2.0 Final has just been released.
In many ways, this release marks the final step for the major forcus of 6.x centered around changing how Hibernate generates SQL. Many improvements in this release, as well as 6.0 and 6.1, have been implemented on top of this SQL AST work. As of 6.0 and 6.1, Hibernate used this SQL AST for loading state from the database. With 6.2, Hibernate also uses SQL AST for writing to the database.
