[hibernate-dev] Scheduling issues
I am trying to determine where we are with 5.3 Final. So I look in Jira and the original 4 issues I added to Final (mainly verification tasks) have jumped to 19. This makes it impossible to plan. So please, if you are not actively working on an issue or are not planning on finishing it within a few days do not schedule it for 5.3.0.Final. Feel free to create a 5.3.1 and schedule it there *if* you are planning on working on it. If you are not planning on working on it do not schedule it. Thanks ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Changes to the ORM Travis configuration
Hi, I committed a few changes to the ORM Travis configuration to hopefully make the builds more stable - we had a lot of failures due to timeouts. As Gradle can spend a lot of time on a specific step without any output, the ORM jobs often timed out. I added a travis_wait 45 to allow the Gradle command to run for 45 minutes. It should be used by the new PRs as soon as you're based on current master. There is one drawback: you only see the command output when it's either finished or timed out but I thought you are probably not spending your time looking at the jobs in progress. Hopefully, it will help. -- Guillaume ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Hibernate ORM 5.1.14.Final released
http://in.relation.to/2018/05/11/hibernate-orm-5114-final-release/ ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
