Re: [DISCUSS] batch patch release voting

2021-12-02 Thread Owen Nichols
ct: 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 f

Re: [DISCUSS] batch patch release voting

2021-12-02 Thread Udo Kohlmeyer
@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

Re: [DISCUSS] batch patch release voting

2021-12-02 Thread Owen Nichols
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 con

Re: [DISCUSS] batch patch release voting

2021-12-02 Thread Udo Kohlmeyer
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

Re: [DISCUSS] batch patch release voting

2021-12-02 Thread Owen Nichols
he 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.

Re: [DISCUSS] batch patch release voting

2021-12-02 Thread 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

Re: [DISCUSS] batch patch release voting

2021-12-02 Thread Donal Evans
o 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 votin

RE: [DISCUSS] batch patch release voting

2021-12-02 Thread Dick Cavender
ber 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

Re: [DISCUSS] batch patch release voting

2021-12-02 Thread 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

[DISCUSS] batch patch release voting

2021-12-01 Thread Owen Nichols
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.