EOL on Release page

[hyandell]

Currently there is no way reliable to state that software is end of life/deprecated or other guidance. It's just information on websites that can't be easily accessed.

While Maven/npm/PyPI etc is one place to try to resolve this, another is GitHub Releases.

When releasing, a project can provide guidance of Pre-Release. It would be excellent if there were more options of guidance available, and that these are then edited over time by the project. The top example being End of Life, aka Do Not Use, aka Not Supported.

If this were added to the Releases page and API, I think it would provide a foundation for projects managing their version guidance more methodically.

[ahpook]

This change is live now 🎉

Blog post with more detail here: https://github.blog/changelog/2022-11-23-repository-archive-date-now-shown-in-ui/

[caniszczyk]

Awesome, thanks, thrilled to see GitHub taking some of these requests :)

…

On Mon, Nov 28, 2022 at 6:14 PM Eric Sorenson ***@***.***> wrote: Closed #77 <#77> as completed. — Reply to this email directly, view it on GitHub <#77 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAPSII54QN22WIQVQCBK33WKTSAFANCNFSM6AAAAAAREOK2QU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Cheers, Chris Aniszczyk https://aniszczyk.org

[hyandell]

Reopening as this was a different issue to the archive date one.

[ahpook]

Oh, d'oh - this was linked from our internal issue and I didn't read closely enough.