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 think it would be worth of exploring.
(1) https://dist.apache.org/repos/dist/release/cassandra/ ________________________________________ From: Tibor Répási <tibor.rep...@anzix.org> Sent: Tuesday, January 31, 2023 12:52 To: dev@cassandra.apache.org Subject: Re: [discussion] Website - information on supported versions NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe. 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 providing these information authoritatively and participate on endoflife.date. Nevertheless, the main issues are * Cassandra’s release process should automatically update that information * the website should be auto-generated using that * some kind of Grafana integration would be appreciated (that’s off-topic here) Also considerable would be to list all versions ever released to distinct on self-built versions. > On 31. Jan 2023, at 12:11, Miklosovic, Stefan <stefan.mikloso...@netapp.com> > wrote: > > 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 > > ________________________________________ > From: Tibor Répási <tibor.rep...@anzix.org> > Sent: Tuesday, January 31, 2023 11:56 > To: dev@cassandra.apache.org > Subject: [discussion] Website - information on supported versions > > NetApp Security WARNING: This is an external email. Do not click links or > open attachments unless you recognize the sender and know the content is safe. > > > > 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 available in a human readable format > only, as far as I see. > > Imagine an organisation running a bunch of Cassandra clusters of different > version, wanting to get an overview. Obviously, we have created a reporting > of versions running and I’ve created some Grafana dashboards showing the > number of nodes, clusters running various versions of Cassandra. Now, I’d > like to extend that with a statistics on how many nodes are running versions > that are up to date, have patches available or running end of life versions. > This should be updated automatically if the state of the upstream project - > Apache Cassandra - changes, due to new release. Rather than parsing the > information from download.html, a source would be nice to have which makes > these information available structured for machine processing. > > What I propose is something available at a fixed URL e.g. > https://cassandra.apache.org/releases.json containing > > { > "latest": [ > "4.1.0", > "4.0.7", > "3.11.14", > "3.0.28" > ], > "stable": { > "version": "4.1.0", > "release": "2022-12-13" > }, > "previous": { > "version": "4.0.7", > "release": "2022-10-23" > }, > "old": [ > { > "version": "3.11.14", > "release": "2022-10-23" > }, > { > "version": "3.0.28", > "release": "2022-10-23" > } > ] > } > > What do you think? > > ~Tibor
