Geode aims for at least 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: 

Branch: develop

Label: blocks-1.16.0

Status: active passive (accepting contributions, but probably still a long way from any thought of cutting a support branch and starting the release processa 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: active (not yet released, but we're working hard to find and fix the last few issues passive (backporting allowed; but a Release Manager has not yet volunteered)

Apache Geode 1.14.

...

5

Release Manager: 

Branch: support/1.14

Label: blocks-1.14.45

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

Apache Geode 1.13.

...

9

Release Manager: 

Branch: support/1.13

Label: blocks-1.13.89

Status: passive (backporting allowed, although we may not ever release 1.13.8 -- see 1.12)

Apache Geode 1.12.9

Release Manager: 

Branch: support/1.12

Label: blocks-1.12.9

Status: approaching end-of-life (backporting allowed.  Once 1.15.0 ships, this branch will be dropped -- unless the project decides to instead drop support/1.13 to satisfy Geode's N-2 support policybut a Release Manager has not yet volunteered)

Past Releases

See https://geode.apache.org/releases