from Hacker News

OpenEoX to Standardize End-of-Life (EOL) and End-of-Support (EOS) Information

by feldrim on 5/12/25, 3:02 PM with 17 comments

• by Hackbraten on 5/12/25, 9:41 PM

  That EoX logo though.

  Every organization or committee that designs a logo should be legally required to have at least one teenager on the board to prevent accidental goatse or other inadvertent blunders.

• by T3OU-736 on 5/12/25, 5:33 PM

  Htm. So, how does this compare, and/or is different from https://endoflife.date?

• by repelsteeltje on 5/12/25, 4:38 PM

  I think it will take a while for people to realize this effort looked great, but wasn't the right approach. Or no silver bullet, at least.

  The presentation with a simple diagram that combines this data with an sbom to yield "information" gives me navel gazing vibes of UML being the future of coding.

  Just as architecture didn't equate to well designed and maintainable software, I fear this initiative won't fix horribly outdated and vulnerable deployments. Software life cycle, deprecation, abandonment, supply chains are mostly a process problem, standards and technology won't fix that.

• by wallrat on 5/12/25, 4:30 PM

  How does this relate to the OWASP/Ecma Common Lifecycle Enumeration Specification (https://tc54.org/cle/)?

• by wpollock on 5/12/25, 4:33 PM

  In my experience, many software projects become abandoned and no notice is given. I don't see how this standard helps in such cases.

• by mud_dauber on 5/12/25, 5:35 PM

  JEDEC has long maintained an EOL/EOS standard for semiconductors. This was a big part of a previous PM gig. Sounds boring, and it was. But having a process kept us out of serious hot water.

• by feldrim on 5/12/25, 3:02 PM

  An SBOM-like approach to EOL/EOS issues is on the way.