3 ms·
I repeatedly google this stuff en mass and thought a community-managed website would be a really great so thank you for saving me loads of effort! I'll be PR-in
by aoeuidiue 7y ago
I repeatedly google this stuff en mass and thought a community-managed website would be a really great so thank you for saving me loads of effort! I'll be PR-ing a bunch of stuff to help out ;)
It may be worth adding a per-version EOL cell, and potential caveats. Windows operating systems, for example, can receive paid support if you happen to have a billion dollars laying around.
Edit: By per-version EOL cell, I mean to allow URL references on a per-version basis for websites that don't list them all on one page, or at all. While there a date-released may also be super useful in some situations when you're trying to figure out how long since it's been patched.
- captn3m0 7y agoMy pet peeve is Python specifically. They have a PEP per release which basically tells you what all will become EOL on this release, which is very confusing. And they also list unsupported releases on the main download page. Can you clarify on the “release cell” part? Not sure what you mean by that. I get you on the Windows part. It took me quite some time to figure out what all is even possible. The Windows page definitely needs a disclaimer.
- aoeuidiue 7y agoSorry I'm not actually sure what they're called but for each release, list the date it was released in a <td>.