Sounds great, Robert. Once your fix is on develop, no further approval is
needed to backport. Use your best judgement (or feel free to discuss on the dev
list if you are unsure). If backporting will take some while, add the
blocks-1.15.0 label to be sure this doesn’t slip through the cracks.
I would like GEODE-1028 [1] to be considered for support/1.15. It is a
significant change to the build logic, and I think would be a benefit to
inclusion in the release branch. PR to develop is available[2]
Thank you,
-Robert Houghton
[1] https://issues.apache.org/jira/browse/GEODE-10283
[2
Great news! I would be delighted to continue as Release Manager for 1.15.0.
To track progress toward code-complete, I will monitor the "needsTriage" and
"blocks-1.15.0" labels (for Affects Version = 1.15.0). Currently I see 1
needsTriage [1] and 2 blocks-1.15.0 [2].
[1]
Owen, with all the recent work I think we are in an excellent position to
resume work on the 1.15 release. While there are a few thing still outstanding,
let’s go ahead and recut the release branch as of Monday, 2022-05-09. Would you
be willing to resume release manager duties?
@Everyone -
Spring Data for Apache Geode (and the upcoming Spring Data for VMware Tanzu
GemFire) very much depends on and uses the Management REST API.
From: Jinmei Liao
Date: Thursday, May 5, 2022 at 5:40 PM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL] RFC for migrating from springfox to springdoc
