Issue Tracking

Hibernate projects use JIRA for issue tracking and project management. 

Reporting Guidelines

• Issue Tracking is not meant for user questions and help.  If you need help, or have questions regarding usage of Hibernate look at the documentation or direct your inquiries to the forums or irc.
• If using JIRA to ask usage questions you will be publicly humiliated in the most painful way possible :)
• If reporting a bug, it is expected that the report be accompanied by a test case reproducing the reported behavior; preferably a JUnit test case.  See the "Test Cases" section below for details

Test Cases

JIRA bug reports without accompanying test cases illustrating and reproducing the reported bugs are generally given far lower priority. Good test cases should be the reduced to the minimum needed to fulfil this "illustrating and reproducing"; in other words, don't just zip up your 10,000 line enterprise application and attach it. This is important for a number of reasons. First, as a good OSS citizen you are expected to attempt to isolate the issue yourself (and maybe even provide a patch!). Secondly it helps the Hibernate developers identify the causes of the bugs and fix them.

These guidelines are generally what we are after.

Hibernate offers a set of classes built on top of JUnit to help developers write TestCases which interact with databases. They take care of many aspects of testing such as building SessionFactories, managing your Session, creating and dropping schemas, etc. These are the infrastructure classes used by the Hibernate functional test suite itself and allow the Hibernate tests to be easily run against multiple databases without code changes.

While it is not required that TestCases accompanying JIRA bug reports use these infrastructure classes, doing so helps the Hibernate developers integrate the tests into the testsuite for continuing regression testing. Have a look at the org.hibernate.junit.functional.FunctionalTestCase and org.hibernate.junit.functional.FunctionalTestClassTestSuite classes.

Contributions

Pull requests are the preferred means of contributing to Hibernate in terms of changes.  We can work with patches, but pull requests make integrating the changes much easier for us and help foster collaboration in applying the changes.  See CONTRIBUTING.md for details on submitting GitHub pull requests.

On to JIRA

Continue to the Hibernate JIRA...