Page History

...

What is different:  in addition to quarterly minor releases, we will provide patch releases for N, N-1, N-2 versions starting with the upcoming 1.12.0 release.  These patch releases would be ad-hoc (as needed) and ideally limited to no more than one per month across each minor version.

What this looks like:

Release 1.11.0 will be superseded by 1.12.0 and receive no patches except as needed under the prior policy.

...

Assuming this is a critical bug, you would make the fix on the /develop branch and back port it onto N, N-1, and N-2 release branches.  Following the release of a new minor version, we will create a /support/x.y branch to use for releasing patch versions.

References

[1] https://cwiki.apache.org/confluence/display/GEODE/Release+Schedule

[2] https://lists.apache.org/thread.html/8626f7cc73b49cc90129ec5f6021adab3815469048787032935bfc1e%40%3Cdev.geode.apache.org%3E

[3] https://cwiki.apache.org/confluence/display/GEODE/Versioning+and+Branching

[4] https://lists.apache.org/thread.html/17d3c1a8644a5147aec63e08530bdf1db61c5cacd1587faf30adf1c1%40%3Cuser.geode.apache.org%3E

...