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 proposed on the dev list and a Release Manager has volunteered, shipping typically takes a month or more. 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.
Apache Geode 1.16.0
Release Manager:
Branch: develop
Label: blocks-1.16.0
Status: active (but probably still a long way from any thought of cutting a support branch and starting the release process)
Apache Geode 1.15.0
Release Manager: Owen Nichols (see email)
Branch: support/1.15
Label: blocks-1.15.0
Status: active-uncertain (not yet released. branch was cut Jan 19. we're working to find and fix issues, but also contemplating delaying this release to include additional features)
Apache Geode 1.14.5
Release Manager:
Branch: support/1.14
Label: blocks-1.14.5
Status: passive (backporting allowed, but a Release Manager has not yet volunteered)
Apache Geode 1.14.4
Release Manager: Dick C
Branch: support/1.14
Label: blocks-1.14.4
Status: active (RC1 was frozen Mar 4; voting expected to take place March 15-18)
Apache Geode 1.13.9
Release Manager:
Branch: support/1.13
Label: blocks-1.13.9
Status: passive (backporting allowed, but a Release Manager has not yet volunteered)
Apache Geode 1.13.8
Release Manager: Dick C
Branch: support/1.13
Label: blocks-1.13.8
Status: voting (RC1 was frozen Mar 3; voting is taking place on the dev list now-March 15)
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)