Re: [VOTE] Apache Geode 1.15.2.RC1

Hi Jinwoo, Appreciate you taking the lead on this. No need to apologize — take your time. On Thu, Sep 4, 2025 at 7:51 AM Jinwoo wrote: > Dear Geode Development Community, > > I would like to extend my sincere apologies as we withdraw voting for > Apache Geode version 1.15.2.RC1. This release ca

Re: [DISCUSS] Draft Geode Release Manager runbook

Hi Kirk, Congrats on the new role, and thanks for everything you’ve done for the project overall! Your support has been super valuable in many areas, Take your time — we really appreciate having you involved. On Thu, Sep 4, 2025 at 12:12 AM Kirk Lund wrote: > I'm preparing to start a new job in

Re: Request for Guidance on Merging Critical Commits to support/1.15

Hi Jinwoo, Sounds good. Looking at support/15: Commits · apache/geode Pls include 2 commits from develop branch: GEODE-7483: Add Generational ZGC (#7896) · apache/geode@93234a5

Request for Guidance on Merging Critical Commits to support/1.15

Hello Geode Development Community, I hope this message finds you well. In the absence of updated information at this time, I am planning to merge critical commits into the support/1.15 branch to facilitate the preparation of a new release candidate. This step is necessary because the current sc

Re: [DISCUSS] Draft Geode Release Manager runbook

Hi Kirk, Thank you for your thoughtful note. I completely understand the demands of starting a new role—especially with travel in the mix. Your continued participation in PMC discussions is genuinely appreciated, and I want to acknowledge the effort you've already put into reviewing the release

Re: [DISCUSS] Draft Geode Release Manager runbook

I'm preparing to start a new job including some travel, so I'm afraid I'm not going to have much time this week. I'll still provide participation and support in PMC discussions, but I'm not going to have time to do any technical digging or reverse engineering of how the old release scripts or pipel

Re: [DISCUSS] Draft Geode Release Manager runbook

Dear Kirk and Community Members, I’ve reviewed the prepare_rc.sh script and noticed that it generates a release candidate from support/1.15, including a commit to update the copyright year. While the script does clone the develop branch, it doesn’t appear to perform any operations on it. This

prepare_rc.sh added only one commits

Hello, I hope you're doing well. It seems that prepare_rc.sh incorporated only a single commit from develop into RC1. https://github.com/apache/geode/commits/rel/v1.15.2.RC1 Would you mind sharing your thoughts on this? I’d appreciate your insight. Thank you in advance. Best regards, Jinwoo

deploy_rc_pipeline failure

Hello Geode Dev Community, I hope you're all doing well. I'm encountering an issue while attempting to deploy the release candidate pipeline: geode/dev-tools/release/deploy_rc_pipeline.sh -v 1.15 The error message I receive is: Error: unknown command "login" for "fly" Did you mean this?   l

[VOTE] Apache Geode 1.15.2.RC1

Hello Geode Dev Community, This is a release candidate for Apache Geode version 1.15.2.RC1. Thanks to all the community members for their contributions to this release! Please do a review and give your feedback, including the checks you performed. Voting deadline: 3PM PST Mon, September 08

Re: [DISCUSS] Draft Geode Release Manager runbook

Hi Calvin and Kirk, Thank you both for your continued support and guidance. With this release iteration, we should be able to improve the documentation. I successfully completed prepare_rc.sh and am now proceeding with committing the release candidate. Regarding LDAP, yes—I typically enter my u

RE: [DISCUSS] Draft Geode Release Manager runbook

Sorry, one more thing... I want to make sure we understand the process correctly. We have been merging pull requests intended for this release (1.15.2) into develop. We will now merge those specific commits into the support/1.15 branch and cut a release candidate, then merge eligible commits fr

Re: [DISCUSS] Draft Geode Release Manager runbook

Hi William, I'm only saying that you don't want to blindly merge all 79 commits to develop. Some of those commits may be specific to support/1.15 and thus not applicable to develop. It's also possible that previous committers already merged some of the applicable commits to develop. I think we'll