|
|
|
|
|
|
by dspillett
922 days ago
|
|
|
Could be a very useful resource. There have been a couple of occasions when I've found it harder than it should be to find EOL information. Of course sometimes there isn't any because many small projects have no official support cycle, but sometimes projects of significance, and even some commercial products, don't either. But sometimes there is and it isn't well documented (or sufficiently linked so it is hard to find). Would you consider adding a timeline-like view, for instance pages listing everything due to go EOL or move between support categories (current, still under standard support, extended (full LTS), extended (limited, i.e. security only or common packages only)) this/next month/quarter/year? Those pages could be static and refreshed daily rather than needing resource to generate on each visit (filtering could be done client-side to allow more flexibility without extra server resource for dynamic generation). This could be done by a 3rd-party, but that might involve scraping the API/site in a way that imparts an unfriendly amount of load (unless I'm missing something, the data in the release-data repo doesn't contain everything that would be needed for this). |
|
|
Generating pages isn't hard for us. We maintain it in our frontmatter/yaml (See https://github.com/endoflife-date/endoflife.date/blob/master... for example). The release-data repo is for tracking new releases of upstream products so we can patch the latest version automatically, and get notified of new major releases that are missing in our tables. release-data is a much smaller subset of our data, and doesn't include the critical EOL data.