Contributing to Spring Session

Spring Session is released under the Apache 2.0 license. If you would like to contribute something, or simply want to hack on the code this document should help you get started.

Please see our code of conduct.

Please see our Security policy.

We use GitHub issues to track bugs and enhancements. If you have a general usage question please ask on Stack Overflow. The Spring Session team and the broader community monitor the spring-session tag.

If you are reporting a bug, please help to speed up problem diagnosis by providing as much information as possible. Ideally, that would include a small sample project that reproduces the problem.

Create your topic branch to be submitted as a pull request from the oldest impacted and supported maintenance branch. You can find the supported versions by looking at the milestones page. Switch to a branch named <major>.<minor>.x from the smallest milestone in the format of <major>.<minor>.<patch>(-<prerelease>). The spring team will ensure the code gets merged forward into additional branches.

All commits must include a Signed-off-by trailer at the end of each commit message to indicate that the contributor agrees to the Developer Certificate of Origin. For additional details, please refer to the blog post Hello DCO, Goodbye CLA: Simplifying Contributions to Spring.