Hi Alberto, For releasing 1.14 we are waiting on two more backports.
GEODE-8609 - DUnit runners were not checking the logs for suspicious errors/fatal messages in VMs that were being restarted in a test. A fix is ready and is in PR review stage[1] GEODE-9289 - A problem with Cluster Configuration where a new locator sends its configuration to an old locator, the old locator is unable to deserialize it, causes NPEs and clears out certain fields in the configuration. A PR is ready and is in review phase but this will need GEODE-8609 checked in first.[2] Once these two PRs are merged and backported, we are going to start the process for voting on the release branch and release candidates. My personal estimate is that we can start with the voting process within next week, if we do not detect any serious issues. Please do reach out if you require any additional information. Regards, Nabarun [1] https://github.com/apache/geode/pull/6526 [2] https://github.com/apache/geode/pull/6495 ________________________________ From: Alberto Gomez <alberto.go...@est.tech> Sent: Monday, May 31, 2021 8:08 AM To: dev@geode.apache.org <dev@geode.apache.org> Subject: Re: [INFO] Apache Geode 1.14.0 Release Manager Hi Naba, Can you please provide some information about how the 1.14 release is going and if is there any planned date for it? Thanks in advance, Alberto ________________________________ From: Nabarun Nag <n...@vmware.com> Sent: Monday, March 22, 2021 5:27 PM To: dev@geode.apache.org <dev@geode.apache.org> Subject: [INFO] Apache Geode 1.14.0 Release Manager Hi everyone, I hope you all are doing well. This is to inform the Apache Geode community that I will be volunteering as the Release Manager for 1.14.0 release. Thank you, Owen, for all the work that has been done to get the release to this point. As for backporting, as a developer, you just need to create a PR against the support/1.14 branch, and you are done. As a release manager, I will take over from there. Just ensure the following: * The PR is a cherry-pick (cherry-pick -x) of a commit that is already in develop * Ensure that there are no merge conflicts. Regards Nabarun Nag
