Geode releases are driven by the community. A release should first be proposed on the dev list, 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.
None, unless someone volunteers for one or more of the following:
Release Manager:
Branch: develop
Label: blocks-1.16.0
Status: passive (accepting contributions, but a Release Manager has not yet volunteered)
Release Manager:
Branch: support/1.15
Label: blocks-1.15.1
Status: passive (backporting allowed; but a Release Manager has not yet volunteered)
Release Manager:
Branch: support/1.14
Label: blocks-1.14.5
Status: passive (backporting allowed, but a Release Manager has not yet volunteered)
Release Manager:
Branch: support/1.13
Label: blocks-1.13.9
Status: passive (backporting allowed, but a Release Manager has not yet volunteered)
See https://geode.apache.org/releases