Contributing

Contribute to the Querydsl development via pull requests. If the pull request is related to a new issue, make sure that the issue is accepted to be fixed by enganging in the Querydsl community via the Querydsl google group or simply by creating an issue in GitHub and asking for opinion.

For more info about pull requests visit https://help.github.com/articles/using-pull-requests

This blog post provides also a good overview of this contribution practice http://spring.io/blog/2010/12/21/social-coding-in-spring-projects

Querydsl release versioning complies to semantic versioning principles defined here http://semver.org/. Therefore by default changes are expected to be backwards compatible. If you provide changes that are not backwards compatible your pull request will be considered for the next major release.

Pull request merge preconditions

Before merging a pull request the following conditions should be met

• PR is not labeled with progress
• Travis build passes
• accepted by someone else than the committer
• has been publicly available for at least 2 days
• for backport PRs 1 day is enough
• backport PRs are automatically accepted by the acceptance of the main PR