:grey_question: About

Apache Maven is a very used and well known buld tool for java.

:bookmark: Related resources

I have used Maven Releases History as a base data for the pull request.

:bar_chart: Maven usage stats

From this tweet :

Preview

• https://deploy-preview-1047--endoflife-date.netlify.app/ansible-core
• https://deploy-preview-1047--endoflife-date.netlify.app/ansible

Hi maintainers, Great project, thank you

I'm part of the Ansible Community team at Red Hat.

Starting with Ansible 2.10, there are two independent packages, both with different release cycles

• [X] Split into two files
• [ ] Update links and references to support
• [ ] Add communication & community links
• [ ] Restore timeline graph
• [ ] Update EOL per release info
• [ ] Update Support per release info
• [ ] Add Python requirments (controller & managed node) table like https://endoflife.date/tomcat

Questions

1. Is https://github.com/endoflife-date/release-data just for info? Or is that data used in addition to releases:?
2. ~~If you could approve GitHub Actions so I can check the new pages are rendered correctly, that would be appreciated.~~ Thanks :)

First attempt also trying to use the automation for GitHub releases based on information at https://opensearch.org/releases.html and https://opensearch.org/docs/latest/version-history/. Might take a few goes!

:information_source: Product info

JReleaser is a release automation tool for Java and non-Java projects. Its goal is to simplify creating releases and publishing artifacts to multiple package managers while providing customizable options.

:point_up: NB

I'm waiting for additional elements from project maintainer cf :

• https://github.com/jreleaser/jreleaser/issues/1082

:point_right: Also, I've only put major versions, please let me know if I should put more details

Sources used:

Release date for crystal well: https://en.wikichip.org/wiki/intel/crystal_well Release date for haswell: https://en.wikipedia.org/wiki/Haswell_(microarchitecture) Release and discontinued date for ivy bridge: https://en.wikipedia.org/wiki/Ivy_Bridge_(microarchitecture) Release date for devil's canyon: https://www.techpowerup.com/cpu-specs/core-i5-4690k.c1762 Discontinued date for devil's canyon: https://ark.intel.com/content/www/us/en/ark/products/80811/intel-core-i54690k-processor-6m-cache-up-to-3-90-ghz.html Discontinued status for crystal well: https://ark.intel.com/content/www/us/en/ark/products/codename/51802/products-formerly-crystal-well.html Release and discontinued date for broadwell: https://en.wikipedia.org/wiki/Broadwell_(microarchitecture) Release and discontinued date for skylake: https://en.wikipedia.org/wiki/Skylake_(microarchitecture) Release date for apollo lake: https://en.wikichip.org/wiki/intel/cores/apollo_lake Discontinued status for bay trail: https://ark.intel.com/content/www/us/en/ark/products/93022/intel-pentium-processor-a1020-2m-cache-up-to-2-66-ghz.html Release date for bay trail: https://www.notebookcheck.net/Intel-introduces-new-Bay-Trail-processors-for-notebooks-desktops-and-all-in-ones.101769.0.html Release date for braswell: https://en.wikichip.org/wiki/intel/cores/braswell I have no source for braswell or cherry tail discontinuation, but I feel it is pretty safe to assume given how old they are and no reseller for their CPUs being found. Release date for cherry tail: https://en.wikichip.org/wiki/intel/cores/cherry_trail Release and discontinued date for Cannon Lake : https://en.wikipedia.org/wiki/Cannon_Lake_(microprocessor) Avoton is simply stating the third quarter of 2013, as that is the only "date" I found: https://en.wikipedia.org/wiki/Silvermont#Server_processors_(Avoton) Similar case with Briarwood: https://en.wikipedia.org/wiki/List_of_Intel_Atom_processors#%22Briarwood%22_(32_nm) Release date for Centerton: https://www.anandtech.com/show/6509/intel-launches-centerton-atom-s1200-family-first-atom-for-servers Release and discontinued date for Kaby Lake: https://en.wikipedia.org/wiki/Kaby_Lake Release date for gemini lake: https://en.wikichip.org/wiki/intel/cores/gemini_lake Discontinued status for gemini lake: https://ark.intel.com/content/www/us/en/ark/products/codename/83915/products-formerly-gemini-lake.html Release and discontinued date for Kaby Lake: https://en.wikipedia.org/wiki/Coffee_Lake Release date for Comet Lake: https://en.wikipedia.org/wiki/Comet_Lake_(microprocessor) Release date for Ice Lake: https://en.wikipedia.org/wiki/Ice_Lake_(microprocessor) Release date for Elkhart lake: https://www.anandtech.com/show/16102/intel-launches-10nm-atom-embedded-cpus-elkhart-lake-now-available Discontinued status for lakefield: https://www.extremetech.com/computing/324435-intel-eols-lakefield-its-first-x86-hybrid-cpu Release date for Lakefield: https://newsroom.intel.com/press-kits/lakefield/ Release date for Tiger Lake: https://en.wikipedia.org/wiki/Tiger_Lake Release date for Jasper Lake: https://www.anandtech.com/show/16388/intel-launches-jasper-lake-tremont-atom-cores-for-all Release date for Rocket Lake: https://en.wikipedia.org/wiki/Rocket_Lake

Sources used:

5.18 EOL date: https://kde.org/announcements/plasma/5/5.18.0/

5.23 EOL date (release of 5.24 was used): https://community.kde.org/Schedules/Plasma_5#Support_status_by_Release_Series

Done #59

There's issue that it can not set absolute value to icalendar's trigger. So I just set 365days, 182days, 90days, 30days to notify 1 year, 6 months, 3 months and 1 month for now.

I'm working on the issue.

Sources used for end of life dates:

Individual releases: https://docs.microsoft.com/en-us/lifecycle/products/?products=internet-explorer

https://docs.microsoft.com/en-us/lifecycle/faq/internet-explorer-microsoft-edge#what-is-the-lifecycle-policy-for-internet-explorer-

Exception for Explorer 7 is due to it being part of Windows Embedded: https://docs.microsoft.com/en-us/lifecycle/products/internet-explorer-7

Right now we are using release tag to mention related cycle's first version date and i am suggesting to rename this one to cycleReleaseDate and add a new tag for the release date of latest tag for related cycle's latest version latestReleaseDate

These two tags will make it less confusing for the contributors and also let our api will be much cleaner

And yes i know it will bring a lttle more burden to us/contributors to add each new/latest versions release dates but i believe we can handle that one

As a summary :
release --> cycleReleaseDate : To mention current series' first version date add latestReleaseDate : To mention the latest version date

• Use the Security Policy instead of the Release Planning for releasePolicyLink. The Security Policy provides better information on supported versions.
• Remove eol and support dates for the last version. Those dates are not predictable.
• Update eol and support dates for all but the last versions. eol and support dates for a version X are the greater date between the releaseDate of the X+1 version and the last patched version.
• Update description : provide better information for the community version, and add a paragraph describing the Red Hat build of Quarkus (RHBQ).

The only weird change here is the Java SE 7's EOL date of 2019. There's differing levels of support for this from different vendors.

RedHat offered support till June 2020

AdoptOpenJDK doesn't list JDK 7.

jdk.java.net explicitly calls it out as an unsupported release:

These binaries are provided primarily for use by implementors of the Java SE 7 Platform Specification and are recommended for reference purposes only. The Reference Implementations have been approved by the JCP and will receive no further updates, not even for security issues. Binaries for development and production use will be available from Oracle and in most popular Linux distributions.

Oracle's own Java at a glance page which we link to, only mentions 8,11, and 16.

However, Oracle's release notes for Java 7 mention JDK 7u311 as the latest release (July 20, 2021)

Oracle's support roadmap page lists 2 dates:

• July 2019 for premier support
• July 2022 for extended support

with this disclaimer:

The Extended Support uplift fee will be waived for the period June 2019 - July 2022 for Java SE 7. The Extended Support uplift fee will be waived for the period March 2022 - December 2030 for Java SE 8. During this period, you will receive Extended Support as described in the Oracle Technical Support Level sections of the Technical Support Policies.

Even with this, I couldn't find a way to install JDK 7u311 without contacting Oracle Sales. Unsure of what to do here. A note in the text perhaps?

https://www.oracle.com/java/technologies/java-se-support-roadmap.html

Aside: https://javadl-esd-secure.oracle.com/update/baseline.version is also a good resource

• document EOL policy,
• simplify the product description.
• remove all minor versions and only track major versions,
• update releasePolicyLink with a more suitable link,
• update 1.x release using https://github.com/cakephp/cakephp/releases/tag/1.3.21,
• update 2.x and 3.x releases using https://github.com/cakephp/cakephp/wiki,
• remove codename and releaseLabel, it was only available on the latest minor release and not widely used.

Link to product page on endoflife.date

https://endoflife.date/cakephp

Details of incorrect and correct details you have found

The 4.3 is still supported, but EOLed. There was also a new releases for EOLed cycles in #2261.

#2157 will add a new extended support column for tracking the dates of extended/commercial support.

Make a pass on all products to see if it make sense to use it.