Re: [DISCUSS] batch patch release voting

[Owen Nichols]

We already do “bulk/batch” release voting, as every vote covers several 
artifacts (geode, geode-native, geode-benchmarks, geode-examples).  I don’t 
interpret the ASF rules as setting any limit on the number of artifacts that 
can be approved in one vote.

It sounds like the rough consensus from this thread is to continue with 
separate votes per patch release, and just combine the announcement.  Thanks 
all for the input.



---
Sent from Workspace ONE Boxer<https://whatisworkspaceone.com/boxer>

On December 2, 2021 at 4:27:05 PM PST, Udo Kohlmeyer  wrote:
I thought that was the case…

Then maybe every release has to be voted on, no bulk/batch allowed, as every 
release has to be verified separately.

Which, just means that bulk announcements is the only thing that makes sense…

From: Owen Nichols 
Date: Friday, December 3, 2021 at 10:39 AM
To: dev@geode.apache.org 
Subject: Re: [DISCUSS] batch patch release voting
I wonder if voting on patch versions makes sense.


Releasing (even patch releases) is an Act of the Apache Software Foundation, 
and as such there is a legal obligation to follow ASF voting rules for every 
release. Technically the purpose of the vote is for the Geode PMC to certify 
that the release meets ASF legal criteria (but there’s never such thing as too 
much testing, so we also hope reviewers will use the opportunity to think up 
creative new ways to test each release candidate)

---
Sent from Workspace ONE 
Boxer<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwhatisworkspaceone.com%2Fboxerdata=04%7C01%7Conichols%40vmware.com%7C5b86a327271442fd31d808d9b5f3a01e%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637740880245084944%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=jPrDfKScZu9TOw%2FtVqNPDQsVL1Y7gU1LrmcndKtYHWg%3Dreserved=0>

On December 2, 2021 at 3:25:03 PM PST, Udo Kohlmeyer  wrote:
I wonder if voting on patch versions makes sense. As we should never be 
breaking any existing features and essentially there should be sufficient 
testing on the fixes to confirm that they resolve the issues. There should also 
be no changes to APIs, as those changes should be included in a new minor.

I think a bulk announcement makes sense… So where possible we should/could 
adopt that approach.

But bulk vote for releases does not, as each patch version might contain 
different amount of fixes, for each minor. (some fixes might only be required 
in older/newer minor versions)

From: Owen Nichols 
Date: Friday, December 3, 2021 at 9:56 AM
To: dev@geode.apache.org 
Subject: Re: [DISCUSS] batch patch release voting
It doesn’t really make a lot of sense to release a fix in a 1.12 patch 
separately without later patches. Doing so would send the confusing message 
that users need to downgrade to get the fix (or if they upgrade they will lose 
it).

So, whether we vote separately or not, we should still probably wait to 
announce all together once all three are ready.


---
Sent from Workspace ONE 
Boxer<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwhatisworkspaceone.com%2Fboxerdata=04%7C01%7Conichols%40vmware.com%7C5b86a327271442fd31d808d9b5f3a01e%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637740880245084944%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=jPrDfKScZu9TOw%2FtVqNPDQsVL1Y7gU1LrmcndKtYHWg%3Dreserved=0>

On December 2, 2021 at 11:47:28 AM PST, Donal Evans  wrote:
The thing I wonder about with this decision is what happens if there are no 
problems with two of the releases, but one of them has some showstopping issue 
that needs to be addressed.

Given that not every fix that's going into 1.14.1 is going into 1.12.6, it's 
possible that an unrelated issue with the 1.14 patch release could hold up the 
release of the perfectly fine 1.12 release if the vote is on releasing all 
three. In that case, would there need to be a new RC for the 1.12 and 1.13 
releases, given that the vote for them would technically have failed? Would 
there need to be a new vote on all three releases, or just go ahead with the 
1.12 and 1.13 release and re-vote on the 1.14 once the issue is fixed?

From: Owen Nichols 
Sent: Wednesday, December 1, 2021 11:45 AM
To: dev@geode.apache.org 
Subject: [DISCUSS] batch patch release voting

Geode's N-2 support policy can lead to "waves" of patch releases.  For example, 
1.12.6, 1.13.5 and 1.14.1 are all likely this month, with many of the same 
fixes in each.

Some open source projects group waves of patch releases into a single 
announcement.  It might be nice to do this for Geode.

For voting, does anyone have any preference whether to still hold three 
separate votes, or would it be ok to vote on a batch of patch releases at once? 
 If so, would 3 days still be enough time for the voting deadline?

Re: [DISCUSS] batch patch release voting

[Udo Kohlmeyer]

I thought that was the case…

Then maybe every release has to be voted on, no bulk/batch allowed, as every 
release has to be verified separately.

Which, just means that bulk announcements is the only thing that makes sense…

From: Owen Nichols 
Date: Friday, December 3, 2021 at 10:39 AM
To: dev@geode.apache.org 
Subject: Re: [DISCUSS] batch patch release voting
I wonder if voting on patch versions makes sense.


Releasing (even patch releases) is an Act of the Apache Software Foundation, 
and as such there is a legal obligation to follow ASF voting rules for every 
release. Technically the purpose of the vote is for the Geode PMC to certify 
that the release meets ASF legal criteria (but there’s never such thing as too 
much testing, so we also hope reviewers will use the opportunity to think up 
creative new ways to test each release candidate)

---
Sent from Workspace ONE 
Boxer<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwhatisworkspaceone.com%2Fboxerdata=04%7C01%7Cudo%40vmware.com%7C4deddca4a14a4d5f8fec08d9b5ed0787%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637740851903182156%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=ISRlc%2BXuR%2F9kNGbWoejBjx5stGD0wfAuoxDmaMj1tx4%3Dreserved=0>

On December 2, 2021 at 3:25:03 PM PST, Udo Kohlmeyer  wrote:
I wonder if voting on patch versions makes sense. As we should never be 
breaking any existing features and essentially there should be sufficient 
testing on the fixes to confirm that they resolve the issues. There should also 
be no changes to APIs, as those changes should be included in a new minor.

I think a bulk announcement makes sense… So where possible we should/could 
adopt that approach.

But bulk vote for releases does not, as each patch version might contain 
different amount of fixes, for each minor. (some fixes might only be required 
in older/newer minor versions)

From: Owen Nichols 
Date: Friday, December 3, 2021 at 9:56 AM
To: dev@geode.apache.org 
Subject: Re: [DISCUSS] batch patch release voting
It doesn’t really make a lot of sense to release a fix in a 1.12 patch 
separately without later patches. Doing so would send the confusing message 
that users need to downgrade to get the fix (or if they upgrade they will lose 
it).

So, whether we vote separately or not, we should still probably wait to 
announce all together once all three are ready.


---
Sent from Workspace ONE 
Boxer<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwhatisworkspaceone.com%2Fboxerdata=04%7C01%7Cudo%40vmware.com%7C4deddca4a14a4d5f8fec08d9b5ed0787%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637740851903182156%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=ISRlc%2BXuR%2F9kNGbWoejBjx5stGD0wfAuoxDmaMj1tx4%3Dreserved=0>

On December 2, 2021 at 11:47:28 AM PST, Donal Evans  wrote:
The thing I wonder about with this decision is what happens if there are no 
problems with two of the releases, but one of them has some showstopping issue 
that needs to be addressed.

Given that not every fix that's going into 1.14.1 is going into 1.12.6, it's 
possible that an unrelated issue with the 1.14 patch release could hold up the 
release of the perfectly fine 1.12 release if the vote is on releasing all 
three. In that case, would there need to be a new RC for the 1.12 and 1.13 
releases, given that the vote for them would technically have failed? Would 
there need to be a new vote on all three releases, or just go ahead with the 
1.12 and 1.13 release and re-vote on the 1.14 once the issue is fixed?

From: Owen Nichols 
Sent: Wednesday, December 1, 2021 11:45 AM
To: dev@geode.apache.org 
Subject: [DISCUSS] batch patch release voting

Geode's N-2 support policy can lead to "waves" of patch releases.  For example, 
1.12.6, 1.13.5 and 1.14.1 are all likely this month, with many of the same 
fixes in each.

Some open source projects group waves of patch releases into a single 
announcement.  It might be nice to do this for Geode.

For voting, does anyone have any preference whether to still hold three 
separate votes, or would it be ok to vote on a batch of patch releases at once? 
 If so, would 3 days still be enough time for the voting deadline?

Re: [DISCUSS] batch patch release voting

[Owen Nichols]

I wonder if voting on patch versions makes sense.


Releasing (even patch releases) is an Act of the Apache Software Foundation, 
and as such there is a legal obligation to follow ASF voting rules for every 
release. Technically the purpose of the vote is for the Geode PMC to certify 
that the release meets ASF legal criteria (but there’s never such thing as too 
much testing, so we also hope reviewers will use the opportunity to think up 
creative new ways to test each release candidate)

---
Sent from Workspace ONE Boxer<https://whatisworkspaceone.com/boxer>

On December 2, 2021 at 3:25:03 PM PST, Udo Kohlmeyer  wrote:
I wonder if voting on patch versions makes sense. As we should never be 
breaking any existing features and essentially there should be sufficient 
testing on the fixes to confirm that they resolve the issues. There should also 
be no changes to APIs, as those changes should be included in a new minor.

I think a bulk announcement makes sense… So where possible we should/could 
adopt that approach.

But bulk vote for releases does not, as each patch version might contain 
different amount of fixes, for each minor. (some fixes might only be required 
in older/newer minor versions)

From: Owen Nichols 
Date: Friday, December 3, 2021 at 9:56 AM
To: dev@geode.apache.org 
Subject: Re: [DISCUSS] batch patch release voting
It doesn’t really make a lot of sense to release a fix in a 1.12 patch 
separately without later patches. Doing so would send the confusing message 
that users need to downgrade to get the fix (or if they upgrade they will lose 
it).

So, whether we vote separately or not, we should still probably wait to 
announce all together once all three are ready.


---
Sent from Workspace ONE 
Boxer<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwhatisworkspaceone.com%2Fboxerdata=04%7C01%7Conichols%40vmware.com%7C96315ce75fc440ed1d8f08d9b5eaf660%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637740843028651711%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=Yup%2BjajzF9eA5NBSgIREfNJ5PsQyspqfSrxhIkWyqGw%3Dreserved=0>

On December 2, 2021 at 11:47:28 AM PST, Donal Evans  wrote:
The thing I wonder about with this decision is what happens if there are no 
problems with two of the releases, but one of them has some showstopping issue 
that needs to be addressed.

Given that not every fix that's going into 1.14.1 is going into 1.12.6, it's 
possible that an unrelated issue with the 1.14 patch release could hold up the 
release of the perfectly fine 1.12 release if the vote is on releasing all 
three. In that case, would there need to be a new RC for the 1.12 and 1.13 
releases, given that the vote for them would technically have failed? Would 
there need to be a new vote on all three releases, or just go ahead with the 
1.12 and 1.13 release and re-vote on the 1.14 once the issue is fixed?

From: Owen Nichols 
Sent: Wednesday, December 1, 2021 11:45 AM
To: dev@geode.apache.org 
Subject: [DISCUSS] batch patch release voting

Geode's N-2 support policy can lead to "waves" of patch releases.  For example, 
1.12.6, 1.13.5 and 1.14.1 are all likely this month, with many of the same 
fixes in each.

Some open source projects group waves of patch releases into a single 
announcement.  It might be nice to do this for Geode.

For voting, does anyone have any preference whether to still hold three 
separate votes, or would it be ok to vote on a batch of patch releases at once? 
 If so, would 3 days still be enough time for the voting deadline?

Re: [DISCUSS] batch patch release voting

[Udo Kohlmeyer]

I wonder if voting on patch versions makes sense. As we should never be 
breaking any existing features and essentially there should be sufficient 
testing on the fixes to confirm that they resolve the issues. There should also 
be no changes to APIs, as those changes should be included in a new minor.

I think a bulk announcement makes sense… So where possible we should/could 
adopt that approach.

But bulk vote for releases does not, as each patch version might contain 
different amount of fixes, for each minor. (some fixes might only be required 
in older/newer minor versions)

From: Owen Nichols 
Date: Friday, December 3, 2021 at 9:56 AM
To: dev@geode.apache.org 
Subject: Re: [DISCUSS] batch patch release voting
It doesn’t really make a lot of sense to release a fix in a 1.12 patch 
separately without later patches. Doing so would send the confusing message 
that users need to downgrade to get the fix (or if they upgrade they will lose 
it).

So, whether we vote separately or not, we should still probably wait to 
announce all together once all three are ready.


---
Sent from Workspace ONE 
Boxer<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwhatisworkspaceone.com%2Fboxerdata=04%7C01%7Cudo%40vmware.com%7C28df3bc387b947f8af8308d9b5e6f61b%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637740825845761890%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=%2FkHGnbf2Lq%2BJiHgiQwg1h1VROKqAcM%2BUtfPee%2B5wYL4%3Dreserved=0>

On December 2, 2021 at 11:47:28 AM PST, Donal Evans  wrote:
The thing I wonder about with this decision is what happens if there are no 
problems with two of the releases, but one of them has some showstopping issue 
that needs to be addressed.

Given that not every fix that's going into 1.14.1 is going into 1.12.6, it's 
possible that an unrelated issue with the 1.14 patch release could hold up the 
release of the perfectly fine 1.12 release if the vote is on releasing all 
three. In that case, would there need to be a new RC for the 1.12 and 1.13 
releases, given that the vote for them would technically have failed? Would 
there need to be a new vote on all three releases, or just go ahead with the 
1.12 and 1.13 release and re-vote on the 1.14 once the issue is fixed?

From: Owen Nichols 
Sent: Wednesday, December 1, 2021 11:45 AM
To: dev@geode.apache.org 
Subject: [DISCUSS] batch patch release voting

Geode's N-2 support policy can lead to "waves" of patch releases.  For example, 
1.12.6, 1.13.5 and 1.14.1 are all likely this month, with many of the same 
fixes in each.

Some open source projects group waves of patch releases into a single 
announcement.  It might be nice to do this for Geode.

For voting, does anyone have any preference whether to still hold three 
separate votes, or would it be ok to vote on a batch of patch releases at once? 
 If so, would 3 days still be enough time for the voting deadline?

Re: [DISCUSS] batch patch release voting

[Owen Nichols]

It doesn’t really make a lot of sense to release a fix in a 1.12 patch 
separately without later patches. Doing so would send the confusing message 
that users need to downgrade to get the fix (or if they upgrade they will lose 
it).

So, whether we vote separately or not, we should still probably wait to 
announce all together once all three are ready.


---
Sent from Workspace ONE Boxer

On December 2, 2021 at 11:47:28 AM PST, Donal Evans  wrote:
The thing I wonder about with this decision is what happens if there are no 
problems with two of the releases, but one of them has some showstopping issue 
that needs to be addressed.

Given that not every fix that's going into 1.14.1 is going into 1.12.6, it's 
possible that an unrelated issue with the 1.14 patch release could hold up the 
release of the perfectly fine 1.12 release if the vote is on releasing all 
three. In that case, would there need to be a new RC for the 1.12 and 1.13 
releases, given that the vote for them would technically have failed? Would 
there need to be a new vote on all three releases, or just go ahead with the 
1.12 and 1.13 release and re-vote on the 1.14 once the issue is fixed?

From: Owen Nichols 
Sent: Wednesday, December 1, 2021 11:45 AM
To: dev@geode.apache.org 
Subject: [DISCUSS] batch patch release voting

Geode's N-2 support policy can lead to "waves" of patch releases.  For example, 
1.12.6, 1.13.5 and 1.14.1 are all likely this month, with many of the same 
fixes in each.

Some open source projects group waves of patch releases into a single 
announcement.  It might be nice to do this for Geode.

For voting, does anyone have any preference whether to still hold three 
separate votes, or would it be ok to vote on a batch of patch releases at once? 
 If so, would 3 days still be enough time for the voting deadline?

Re: [DISCUSS] batch patch release voting

[Robert Houghton]

I would hope that all RCs had been checked thoroughly before any release VOTE 
occurs.

From: Donal Evans 
Date: Thursday, December 2, 2021 at 11:47 AM
To: dev@geode.apache.org 
Subject: Re: [DISCUSS] batch patch release voting
The thing I wonder about with this decision is what happens if there are no 
problems with two of the releases, but one of them has some showstopping issue 
that needs to be addressed.

Given that not every fix that's going into 1.14.1 is going into 1.12.6, it's 
possible that an unrelated issue with the 1.14 patch release could hold up the 
release of the perfectly fine 1.12 release if the vote is on releasing all 
three. In that case, would there need to be a new RC for the 1.12 and 1.13 
releases, given that the vote for them would technically have failed? Would 
there need to be a new vote on all three releases, or just go ahead with the 
1.12 and 1.13 release and re-vote on the 1.14 once the issue is fixed?

From: Owen Nichols 
Sent: Wednesday, December 1, 2021 11:45 AM
To: dev@geode.apache.org 
Subject: [DISCUSS] batch patch release voting

Geode's N-2 support policy can lead to "waves" of patch releases.  For example, 
1.12.6, 1.13.5 and 1.14.1 are all likely this month, with many of the same 
fixes in each.

Some open source projects group waves of patch releases into a single 
announcement.  It might be nice to do this for Geode.

For voting, does anyone have any preference whether to still hold three 
separate votes, or would it be ok to vote on a batch of patch releases at once? 
 If so, would 3 days still be enough time for the voting deadline?

Re: [DISCUSS] batch patch release voting

[Donal Evans]

The thing I wonder about with this decision is what happens if there are no 
problems with two of the releases, but one of them has some showstopping issue 
that needs to be addressed.

Given that not every fix that's going into 1.14.1 is going into 1.12.6, it's 
possible that an unrelated issue with the 1.14 patch release could hold up the 
release of the perfectly fine 1.12 release if the vote is on releasing all 
three. In that case, would there need to be a new RC for the 1.12 and 1.13 
releases, given that the vote for them would technically have failed? Would 
there need to be a new vote on all three releases, or just go ahead with the 
1.12 and 1.13 release and re-vote on the 1.14 once the issue is fixed?

From: Owen Nichols 
Sent: Wednesday, December 1, 2021 11:45 AM
To: dev@geode.apache.org 
Subject: [DISCUSS] batch patch release voting

Geode's N-2 support policy can lead to "waves" of patch releases.  For example, 
1.12.6, 1.13.5 and 1.14.1 are all likely this month, with many of the same 
fixes in each.

Some open source projects group waves of patch releases into a single 
announcement.  It might be nice to do this for Geode.

For voting, does anyone have any preference whether to still hold three 
separate votes, or would it be ok to vote on a batch of patch releases at once? 
 If so, would 3 days still be enough time for the voting deadline?

RE: [DISCUSS] batch patch release voting

[Dick Cavender]

+1 for batching them. 

Is it implied with a +1 vote that all the releases have been checked or can you 
only vote on a single release if that's all you checked? We can define this 
when we send out the vote email. 

-Original Message-
From: Robert Houghton  
Sent: Thursday, December 2, 2021 11:26 AM
To: dev@geode.apache.org
Subject: Re: [DISCUSS] batch patch release voting

In the case where its one change being backported all over, I say batch up the 
vote.

From: Owen Nichols 
Date: Wednesday, December 1, 2021 at 11:46 AM
To: dev@geode.apache.org 
Subject: [DISCUSS] batch patch release voting Geode's N-2 support policy can 
lead to "waves" of patch releases.  For example, 1.12.6, 1.13.5 and 1.14.1 are 
all likely this month, with many of the same fixes in each.

Some open source projects group waves of patch releases into a single 
announcement.  It might be nice to do this for Geode.

For voting, does anyone have any preference whether to still hold three 
separate votes, or would it be ok to vote on a batch of patch releases at once? 
 If so, would 3 days still be enough time for the voting deadline?

Re: [DISCUSS] batch patch release voting

[Robert Houghton]

In the case where its one change being backported all over, I say batch up the 
vote.

From: Owen Nichols 
Date: Wednesday, December 1, 2021 at 11:46 AM
To: dev@geode.apache.org 
Subject: [DISCUSS] batch patch release voting
Geode's N-2 support policy can lead to "waves" of patch releases.  For example, 
1.12.6, 1.13.5 and 1.14.1 are all likely this month, with many of the same 
fixes in each.

Some open source projects group waves of patch releases into a single 
announcement.  It might be nice to do this for Geode.

For voting, does anyone have any preference whether to still hold three 
separate votes, or would it be ok to vote on a batch of patch releases at once? 
 If so, would 3 days still be enough time for the voting deadline?