Removed EOL information

[Cherabhi]

Since it is no longer needed

[AKippins]

I don’t think we should remove release notes or lifecycle entries for EOL versions.

Release notes are part of the product’s historical record and are still valuable for troubleshooting, auditability, and understanding version changes over time—especially in enterprise environments where older versions may persist longer than expected.

Similarly, the lifecycle table should remain complete. Removing EOL entries breaks version lineage and obscures upgrade paths. Standard practice is to retain these entries but clearly mark them as EOL / no longer supported, optionally moving them to an “archived” section if we want to reduce clutter.

In short, EOL should be a labeling and visibility decision, not a deletion decision.

[AKippins]

EOL status should affect visibility and labeling, not historical availability. Release notes are part of the product’s operational record, and removing them breaks traceability, supportability, and upgrade clarity. A better approach would be to retain them with clear EOL labeling or move them to an archived section rather than deleting them.

[AKippins]

Note: This lifecycle table intentionally retains all releases, including End-of-Life (EOL) versions, to maintain a complete and auditable product history. While EOL releases are no longer supported, their inclusion ensures continuity, supports upgrade planning, and preserves traceability for troubleshooting and compliance purposes.

I'd suggest updating the table so that it's currently accurate rather than deleting the old releases and the links to the the older references. I believe version 1.3 is when the collection became stable so that's the first version listed here.