Re: [discussion] Website - information on supported versions

Hi Tibor, there is also this: https://endoflife.date/apache-cassandra https://issues.apache.org/jira/browse/CASSANDRA-17788 Maybe you could integrate with this or make it even better? I think it offers some API to query it but I was not digging deep. Regards

Re: [discussion] Website - information on supported versions

Endoflife is currently collecting some information and publishing it, which is not authoritative. E.g. they are reporting eol dates as they would be announced by the project. As discussed on the side band and also mentioned in CASSANDRA-177788, the ideal approach could be that the project is

[discussion] Website - information on supported versions

Hy Everyone, I was thinking about the information available on https://cassandra.apache.org/_/download.html about current and former releases, release dates, supported and unsupported versions of Apache Cassandra. These information are all

Re: Merging CEP-15 to trunk

To clarify: my suggestion was not to block anything or block on green Jenkins. Running there was a suggestion for sanity check and because packaging and burn tests are run only in Jenkins. Also, to summarize, I had a few honest questions around things we expect on any ticket or which I am not

Re: Merging CEP-15 to trunk

> Don't we follow a principle of always shippable trunk? Also, I feel compelled to call out: we don't have perf regression testing we're doing publicly on the project, don't have code coverage analysis, and don't have long-running harry / nemeses-based soak testing to suss out subtle timing

Re: Merging CEP-15 to trunk

> Don't we follow a principle of always shippable trunk? This was actually a > reason why I sidelined the talk about post-merge review, because it implies > that the code wasn't "good enough"/perfect when it was first merged. We follow a principle of "always shippable trunk according to

Re: [discussion] Website - information on supported versions

Hi Tibor, I think that the dumping of versions with their life cycles might be done at the end of the release process. We push the distribution artifacts here (1). Hence the idea is to upload there one json with all the information you want. As soon as we push it there, it will be available. I

Re: Merging CEP-15 to trunk

> About this merge - I would personally love to see everything rebased and > things rerun in CI which no one has a doubt it will happen Yes, I think this is expected behavior that must happen before adding to trunk, or even just rebasing the feature branch; CI must be passing and flaky tests

Re: Merging CEP-15 to trunk

Thanks David, I think I am personally aligned with what you are saying. Thanks for clarifying your previous email. “ I do not believe anyone is arguing to merge Accord with bugs… bugs we know about are blockers for merge. There are pending improvements and features people are working on, but I