+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 <rhough...@vmware.com> 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 <onich...@vmware.com> Date: Wednesday, December 1, 2021 at 11:46 AM To: dev@geode.apache.org <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?
