endoflife-date / endoflife.date Goto Github PK
View Code? Open in Web Editor NEWInformative site with EoL dates of everything
Home Page: https://endoflife.date
License: MIT License
Informative site with EoL dates of everything
Home Page: https://endoflife.date
License: MIT License
Hi in drupal page in table last release is 7.78 not 7.69, below the table the string:
Drupal 7 will receive security patches until November 2021.
is wrong, the table rightly report 2022-11-28 as security eol, here is the link of extension page
https://www.drupal.org/psa-2020-06-24
regards.
Is your feature request related to a problem? Please describe.
iPhone and macOS all start from the low case letter, thus, they are sorted to the end of the sider bar. I think this is unexpected and should be changed.
Describe the solution you'd like
Change iPhone & macOS to Apple iPhone and Apple macOS
Describe alternatives you've considered
change the sorting methods and not differentiate upper case and lower case letter.
What do you guys think?
On the last column (Release), all supported releases should get a link to the respective changelog or upgrade/migration page.
Result: https://endoflife.date/ubuntu
It should be 18.10 instead of 18.1
It will be nice to bump bootstrap version from 4.5.3 to 4.6.0
We should switch away from the sitemap plugin to a custom sitemap, which should include:
Our current generated sitemap: https://endoflife.date/sitemap.xml, only includes very few pages. We want this to be more exhaustive.
Regarding ubuntu LTS your eol page says:
This page does not track ESM (Paid support beyond 5 years for limited set of packages) releases.
but you do. For example, the end of support for ubuntu 16.04 is april 2021 as you wrote for "active support" but this is standard support, instead eol april 2024 is right but only esm customers receive security support from 2021 to 2024. So real eol should be april 2021 if you don't track esm.
While it's good to see "3 years 56 days ago", it would be great to somehow see the dates (YYYY-mm-dd).
Currently items that are dropping support soon (e.g 2 days, 1 month, ...) are colored green. This gives impression that they are good to use, while it would be wiser to move to a newer version that have longer support.
Such items could be highlighted with a different color. Yellow perhaps? However, the next question is: what should be considered a good lower limit for "soon"? Six months?
Make use of scrapers and nightly pipelines to check and update info for the different tools. At https://github.com/projectlint/OS-lifecycle I have something like this, just only I need to finish to tune-up :-)
Assuming you subscribe to the PHP RSS Feed. I would want to get notified on the following scenarios:
RSS Spec allows publication with dates in the future, but it is left to the tool:
If it's a date in the future, aggregators may choose to not display the item until that date.
It would be better to hide the element till the date>=today
for that item, in which we case, uncomment it.
With that in place, (1) should be doable. But how do we get to (2)?
The website (and YAML internally) uses "tool" in a few places. However, "product" seems like a much better term for what all we track (hardware/software/saas/self-hosted/frameworks/operating-systems etc).
I got the idea after @usta's suggestion in #283.
The API doesn't use "tool" anywhere, so it shouldn't be impacted. Shouldn't be hard to change, if others agree. Feedback please?
On Windows Server page, the Security Support Date currently announced for Windows Server 2012 R2 is (12 Jan 2027)
.
But this seams to be wrong. On Microsoft LifeCycle Web site, it's 10/10/2023.
Currently the Java/OpenJDK page lists the EOL dates for commercial Oracle builds:
Java 8 - Mar 2022/Mar 2025
Java 11 - Sep 2023/Sep 2026
https://www.oracle.com/technetwork/java/java-se-support-roadmap.html#JavaSESupport
I would find it helpful to also list the EOL dates for free OpenJDK builds. Eg for AdoptOpenJDK:
Java 8 - Sep 2023
Java 11 - Sep 2022
https://adoptopenjdk.net/support.html#roadmap
Hey! I appreciate the effort to build this website. It is a big help in having one source of truth on EoLs of our most used tools.
I know this might be early but can I request to organize the post markdown files inside a directory (i.e. tools/*.md
)?
I'm happy to do this too!
Cheers!
It is hard to find a decent site that contains the Android OS release plan. There's this wikipedia page though that contains the release date but no "end of dates".
I can suggest adding the distribution graph for more visibility on usage of different OS versions.
Thoughts?
For Node.js the even-numbered releases (12, 14, etc.) become LTS after six months. It would be nice if we can enter the upcoming date as lts: 2021-10-26
and the LTS flag will be there after the specified date.
The reason the line wrapping in the top navigation is messed up (see this thread on HN) is because there's no whitespace between the closing </a>
and the opening <a>
of the next item. This means the browser sees it as one long word, with spaces only where there's spaces in the names of items. You can see this if you try and copy it:
Alpine LinuxCentOSDebianDjangoDrupalFedora LinuxiPhoneLaravelMariaDBNodeJSPHPPythonRHELRubySymfonyUbuntuWindows
You could fix it by adding spaces between the links, or by doing the semantically correct thing and making it an unordered list (something like this).
#61 add a pseudo-API rendering the info in JSON files, but just only for each one of the versions. Add new pages showing the full info for each tool, or maybe also one for ALL the tools at once.
Firstly, this is a great idea and is really needed in the industry 👍
I would however like to propose that a machine readable format is generated. Maybe JSON?
The minor version of Elasticsearch can be double digit, e.g. 7.10 and 7.11. The sorting by releaseCycle is wrong in this case, e.g. 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, 7.11, 7.10.
In #195 I did a workaround with a virtual number in cycleShortHand and sorted by this. I think this could be a problem also in other tools.
The idea is to extend the sorting of such version numbers in _layouts/post.html
.
Previous discussion:#41 (comment)
Write a bit of JS to hide any releases that have a end-of-life date more than 5 years in the past by default. Add a new button on the site that can be used to "show old releases".
When checking this site for the EOL information for a given tool, it's unclear when the page was last modified and thus if the information is current or out of date which seems somewhat antithetical to the purpose of this project.
Ideally the Last Modified date would be generated programmatically, but at the very least could be hard coded on each page and made a requirement for merging any pull request that updates a tool's info.
Is your feature request related to a problem? Please describe.
A visual timeline makes it easier to plan version updates.
Describe the solution you'd like
I think those should be generated from the data for all tools.
Describe alternatives you've considered
Now that there's a bit more community contribution, and we have a lot more velocity thanks to @BiNZGi, I was considering moving this repo under a separate organization. I'm not as active as I'd like to be, and moving to an org might help us with more contributors?
I've pre-booked https://github.com/endoflife-date and if everyone agrees, I'll move across the repository and grant the same access to all existing contributors.
Thoughts @jhnferraris @BiNZGi ?
The Windows support dates to not align with the mainstream and extended support listed below. This link should be added to the page as well.
https://docs.microsoft.com/en-us/windows/release-health/release-information
Semi-Annual Channel
Version | Servicing option | Availability date | OS build | Latest revision date | End of service: Home, Pro, Pro Education, Pro for Workstations and IoT Core | End of service: Enterprise, Education and IoT Enterprise |
---|---|---|---|---|---|---|
20H2 | Semi-Annual Channel | 2020-10-20 | 19042.964 | 2021-04-28 | 2022-05-10 | 2023-05-09 |
2004 | Semi-Annual Channel | 2020-05-27 | 19041.964 | 2021-04-28 | 2021-12-14 | 2021-12-14 |
1909 | Semi-Annual Channel | 2019-11-12 | 18363.1533 | 2021-04-22 | 2021-05-11 | 2022-05-10 |
1809 | Semi-Annual Channel | 2019-03-28 | 17763.1911 | 2021-04-22 | End of service | 2021-05-11 |
1809 | Semi-Annual Channel (Targeted) | 2018-11-13 | 17763.1911 | 2021-04-22 | End of service | 2021-05-11 |
1803 | Semi-Annual Channel | 2018-07-10 | 17134.2145 | 2021-04-13 | End of service | 2021-05-11 |
1803 | Semi-Annual Channel (Targeted) | 2018-04-30 | 17134.2145 | 2021-04-13 | End of service | 2021-05-11 |
Enterprise and IoT Enterprise LTSB/LTSC editions
Version | Servicing option | Availability date | OS build | Latest revision date | Mainstream support end date | Extended support end date |
---|---|---|---|---|---|---|
1809 | Long-Term Servicing Channel (LTSC) | 2018-11-13 | 17763.1911 | 2021-04-22 | 2024-01-09 | 2029-01-09 |
1607 | Long-Term Servicing Branch (LTSB) | 2016-08-02 | 14393.4350 | 2021-04-13 | 2021-10-12 | 2026-10-13 |
1507 (RTM) | Long-Term Servicing Branch (LTSB) | 2015-07-29 | 10240.18906 | 2021-04-13 | End of service | 2025-10-14 |
Here is an error on PostgreSQL page. Latest release for branch 9.5 is shown as 10.2.24. Correct value is 9.5.17.
It makes sense to sort by release date (in desc order
so newer releases are at the top).
The more you have to scan to find your release, the higher
chances of it being EoL are.
Since releases are a map currently, it is hard to sort them.
See #23 for related effort
Would it be possible to put this data into JSON arrays so something like curl https://endoflife.date/json/ubuntu
would work?
Hi,
debian release is wrong, last is 10.10 released on june 19th.
Best regards
Hi!
The Ubuntu page says that it "does not track ESM releases" yet it has the ESM-only dates listed in the "End of Life" column.
E.g. Ubuntu 14.04 EoL was on 2019-04-1, only ESM support is available after that date.
Thanks,
-Michael
I am not a web developer but there is a problem about generated .map file for assets/css/just-the-docs-default.css
Source map error: Error: JSON.parse: expected ',' or ']' after array element at line 56 column 1018 of the JSON data
Discussed previously on HN: https://news.ycombinator.com/item?id=20034030
I tried it out, and while Safari doesn't let you subscribe to a calendar directly, you can add it to iOS via Settings->Accounts->Add Account->Others->Subscribe to Calendar configuration.
A simple ICS file that provides a notification 1 year, 6 months, 3 months, 1 month, 1 week, and on the day of EoL is what I'm planning for.
Deploy preview URLs are hard to use, because every link on the left becomes an absolute URL.
iPhone 12 models are released. Picking this up.
The idea: Make a list of all the tools we support available through the endoflife.date API. That way, someone can use the API without the need to know the exact tool name and url.
For example, we could generate a JSON at https://endoflife.date/api/all.json containing a list with every name and type available in our tools/ folder. Someone could request that JSON, iterate over the array and get all the data, one after another, via https://endoflife.date/api/{names[i]}
Alternatively, we could let any GET routed to https://endoflife.date/all fetch all JSON files/generations available server-side, merge them to a big JSON and return that.
Spring Boot is the most used Web Development framework in Java and Kotlin. EOLs for Spring Boot are lost easily. It is good to have it here.
Could we have a feature that allows subscribing by email to allow users to get updates for tech they choose at given intervals.
Describe the solution you'd like
As a start getting an email digest on selected technology will be sufficient.
Would be helpful to include a section showing support phases and EoL dates for Amazon Linux.
Amazon Linux
https://aws.amazon.com/amazon-linux-ami/
Standard support for Amazon Linux ended 12/31/2020 with maintenance support available through 06/30/2023 for a reduced set of packages and AWS EC2 features/platforms:
https://aws.amazon.com/blogs/aws/update-on-amazon-linux-ami-end-of-life/
Additional support statements for Amazon Linux are available here, and it would be nice if the endoflife site could include a link for those wanting package-specific support information:
https://amazonlinux.github.io/al1-support-statements/
Amazon Linux 2
https://aws.amazon.com/amazon-linux-2/
LTS for Amazon Linux 2 through 06/30/2023:
https://aws.amazon.com/amazon-linux-2/faqs/
What about adding SUSE and openSUSE EOL dates to endoflife.date?
I'm not quite familiar with our underlying ecosystem. I guess we're parsing official APIs and Websites to collect all the data. Unfortunately, I didn't find an official page for openSUSE, but I did for SUSE: https://www.suse.com/lifecycle/
At https://en.opensuse.org/Lifetime#Discontinued_distributions, there is a list of distributions those lifetime has already ended.
I did not find anything for current versions of openSUSE, though.
As per the readme:
If you'd like to hack on how the site gets built, see HACKING.md.
There is no HACKING.md file.
This issue will be resolved when a HACKING.md file exists, containing instructions for how to hack on the project.
Laravel moved to Semver as of 6.0 and therefore 6.1 is wrong and shouldn't really be listed.
https://whichlaravel.me/ shows the correct dates.
It's great to have K8s version EOL dates, EOL dates across managed K8s offerings across Amazon Elastic Kubernetes Service (EKS), Azure Kubernetes Service(AKS), GKE(Google Kubernetes Engine) are different. It would be great to add these as services as well
Wanted: A logo design that can help create an identify for the website. Something that fits with the color scheme is preferred.
I'd also want to see if generic cards can be designed for social media platforms. So sharing the Alpine Linux page gets you a social card with the alpine logo alongside endoflife.date logo.
Do these cards support SVG format that we can generate using Jekyll?
Google sends me these reports once a month. Here's the export for the last 3 months. Covers what kind of searches lead users to the website, splits by countries/devices etc.
https _endoflife.date-Performance-on-Search-2021-01-02.zip
This is from Oct-Dec 2020. I can keep updating this thread over time if anyone thinks this is useful.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.