I am +1 (nb) for 5.0. -0 for 4.0 and 4.1.

I would rather promote people upgrade to the latest release to get new features.

I also think we have been doing a pretty good job of backwards compatibility lately, so I would also promote the side projects using the latest release to work with data from older releases.  If that doesn’t work then it means we have something to fix in the current release in terms of backwards compatibility.

-Jeremiah


On Aug 5, 2024, at 11:04 AM, Jeff Jirsa <jji...@gmail.com> wrote:


As Josh mentioned previously, not all procedural votes treat -1s as vetoes. 

I remain against the backport to 4.0 and 4.1, but not a veto. -1 for those branches. 


On Aug 3, 2024, at 11:19 PM, Yifan Cai <yc25c...@gmail.com> wrote:


Hi,

I am proposing backporting CASSANDRA-19800 to Cassandra-4.0, 4.1 and 5.0. 

There is a discussion thread on the topic. In summary, the backport would benefit Cassandra Analytics by providing a unified solution, and the patch is considered low-risk. While there are concerns about adding features to 4.0 and 4.1, there is generally support for 5.0.

The vote will be open for 72 hours (longer if needed). Votes by PMC members are considered binding. A vote passes if there are at least three binding +1s and no -1's.

Kind regards,
Yifan Cai

Reply via email to