THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Geode aims for about one minor release a year, and usually a few patch releases in between. After a release is releases are driven by the community. A release should first be proposed on the dev list and a Release Manager has volunteered, shipping typically takes a month or more, then a PMC member must volunteer as Release Manager. See Backporting Tips if you'd like to include a major/critical fix in a release after the support branch has been cut.
Upcoming Releases
Plans may change, but here's what might be next.None, unless someone volunteers for one or more of the following:
Apache Geode 1.
...
16.0
Release Manager: Owen Nichols (see email)
Branch: develop
Status: active passive (hoping to be ready to cut a new support/1.15 branch ~June 2022 and ship ~July 2022accepting contributions, but a Release Manager has not yet volunteered)
Apache Geode 1.
...
15.
...
1
Release Manager:
Branch: support/1.1415
Status: passive (backporting allowed, ; but a Release Manager has not yet volunteered)
Apache Geode 1.14.
...
5
Release Manager: Dick C
Branch: support/1.14
Label: blocks-1.14.45
Status: active (RC1 was frozen Mar 4; voting is taking place now through March 18, 2022 passive (backporting allowed, but a Release Manager has not yet volunteered)
Apache Geode 1.13.9
Release Manager:
...
Label: blocks-1.13.9
Status: passive (backporting allowed, but a Release Manager has not yet volunteered)
Apache Geode 1.12.10
Release Manager:
Branch: support/1.12
Label: blocks-1.12.10
Status: approaching end-of-life (backporting allowed, although once 1.15.0 ships, this branch may be dropped as per Geode's N-2 support policy)