A third option, is to cut the branch as normal, and be ready to revert if we see some kind of issue as we are stabilizing the redis changes
On Jan 25, 2022 17:10, Alexander Murmann <amurm...@vmware.com> wrote: Hi everyone, Last week we discussed to cut the 1.15 release branch. I would like to propose that we cut the branch from last week's SHA 8f7193c827ee3198ae374101221c02039c70a561. The following commit is a very large refactor. Nothing obvious seems wrong with that change, but given that we frequently only discover very subtle, but important changes to Geode after a long time, I think that this would allow us to reduce some risk for 1.15 and its future users and give this large change some time to proof itself on the develop branch. I'd love to avoid that work entirely, but am concerned that we only might find out about problems a few weeks from now or worse, after we shipped. Another option might be to branch from head and revert the change on the release branch. I am uncertain which approach will proof less work.
