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: 

...

Label: blocks-1.16.0

Status: active passive (accepting contributions but no definite plans if or when to ship...perhaps 2023 or 2024? maybe as 1.16 or maybe as 2.0?, but a Release Manager has not yet volunteered)

Apache Geode 1.15.

...

1

Release Manager: Owen Nichols (see email) 

Branch: support/1.15

Label: blocks-1.15.01

Status: frozen in preparation for release (may be ready to begin voting on RC1 as early as June 15 passive (backporting allowed; but a Release Manager has not yet volunteered)

Apache Geode 1.14.5

Release Manager: 

...

Label: blocks-1.14.5

Status: passive (backporting allowed, but a Release Manager has not yet volunteered)

...

Label: blocks-1.13.9

Status: inactive (backporting may be skipped, as no further patch releases are likely)

Apache Geode 1.12.10

Release Manager: 

Branch: support/1.12

Label: blocks-1.12.10

Status: passive passive (backporting allowed, but a Release Manager has not yet volunteered)

...