Even a small change can have subtle but important effects only discovered after
a long time, so leaning on commit-size as a proxy for risk may only serve to
create a false sense of security.
Also to consider, having a large refactor on develop but not support/1.15 will
increase backporting pain
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 wrote:
Hi everyone,
Last week we discussed to cut the 1.15 release branch. I would like to propose
that we cut th
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
frequ
The Apache Geode community is pleased to announce the availability of
Apache Geode 1.14.3.
Geode is a data management platform that provides a database-like consistency
model, reliable transaction processing and a shared-nothing architecture
to maintain very low latency performance with high concu
Today is the voting deadline and we have enough to close the vote.
Voting status
==
+1: 4 binding votes
* Donal Evans (PMC member)
* Udo Kohlmeyer (PMC member)
* Dave Barnes (PMC member)
* Eric Shu (PMC member)
+0: zero votes
-0: zero votes
-1: zero votes
The voting meets the requirem
@Raymond any update on who will cut the branch and what time today?
On 1/20/22, 5:20 PM, "Owen Nichols" wrote:
+1
@Raymond are you volunteering as Release Manager or asking for a volunteer?
If the role is still open, I'd be happy to volunteer.
On 1/20/22, 2:18 PM, "Raymond Ingle
