Add /releases and /eol pages#2750
Conversation
|
🙈 The PR is closed and the preview is expired. |
holly-cummins
force-pushed
the
add-releases-page
branch
3 times, most recently
from
a96525f to
b1fdf6e
Compare
|
This should probably include updating the existing /security page which until now listed the overarching version supported ranges. Just to avoid divergence. |
Ah good point, thanks! I hadn't spotted they were listed there. Will update that page to pull from the same data source. (At the moment it's hardcoded in security.adoc.) However, I think I'll do that in a follow-on PR, to not block this one, since it would be an infra change, not a visible one. Well, I guess we'd want to link to /eol on the security page. So I'll do that as well. |
holly-cummins
force-pushed
the
add-releases-page
branch
from
56dcdb5 to
6d90aa9
Compare
Add _data/releases.yaml with version history, LTS flags, support dates, and EOL information for all Quarkus releases. This data is used by the guides tests to dynamically discover which versions to test. Extracted from the /releases and /eol pages work (PR quarkusio#2750).
Add _data/releases.yaml with version history, LTS flags, support dates, and EOL information for all Quarkus releases. This data is used by the guides tests to dynamically discover which versions to test. Extracted from the /releases and /eol pages work (PR quarkusio#2750).
holly-cummins
force-pushed
the
add-releases-page
branch
3 times, most recently
from
762cf37 to
2e85dcb
Compare
This comment has been minimized.
This comment has been minimized.
Add a releases page showing all Quarkus versions with support status, LTS badges, code.quarkus.io links for supported versions, and linked RHBQ/IBM/HeroDevs support badges. Add an end-of-life page explaining EOL consequences with enterprise support options from HeroDevs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
holly-cummins
force-pushed
the
add-releases-page
branch
from
2e85dcb to
97a198d
Compare
Status for workflow
|
3 participants
This is something we've been wanting to do for ages, so that people don't have to go to https://endoflife.date/quarkus-framework to find information we should be providing ourselves.
I've added a releases page showing all Quarkus versions with support status, LTS badges, code.quarkus.io links for supported versions, and linked RHBQ/IBM/HeroDevs support badges. I also added an end-of-life page, modelled on https://node.js/eol, explaining EOL consequences with enterprise support options from HeroDevs.
The releases page is linked off the learn menu (and itself links to the /support page). The /eol page is just linked from the /releases page.
As a tactical first step the data file is manually generated and maintained, but of course my intention is to automate the process of collecting the data (or at least the skeleton of the data).