Hi Jinwoo, Sounds good. Looking at support/15: Commits · apache/geode <https://github.com/apache/geode/commits/support/1.15/>
Pls include 2 commits from develop branch: GEODE-7483: Add Generational ZGC (#7896) · apache/geode@93234a5 <https://github.com/apache/geode/commit/93234a5e9aea25c7ef80cd2ec337e0605871af48> GEODE-10453 - in case of REMOVE_DUE_TO_GII_TOMBSTONE_CLEANUP and Comp… · apache/geode@d834e94 <https://github.com/apache/geode/commit/d834e947cc892a6677f7f82b45cd9d419c13f824> git-flow is so unnatural. It's been long deprecated into legacy: Gitflow Workflow | Atlassian Git Tutorial <https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow> We had one project at work using it as an experiment and it was not successful. Thank you! On Wed, Sep 3, 2025 at 12:53 PM Jinwoo Hwang <jinwoo.hw...@sas.com.invalid> wrote: > 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 > script restricts any interventions between the support branch and the > release candidate during its runtime, preventing me from incorporating > commits once the process is underway. > > I would sincerely appreciate any insights or advice you may have regarding > this approach. Thank you in advance for your time and support. > > > Best regards, > > Jinwoo Hwang (he/him/his) > > > > SAS® Research and Development > > http://JinwooHwang.com<http://jinwoohwang.com/> > > >
