Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update .NET tags EOL policy #6157

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

lbussell
Copy link
Contributor

This update to the tags lifecycle policy is meant to bring it more in line with .NET's official support policy:

End of life refers to the date when Microsoft no longer provides fixes, updates, or online technical assistance.

@lbussell lbussell added the needs-announcement An announcement is needed to discuss customer impact label Jan 17, 2025
@lbussell lbussell requested a review from a team as a code owner January 17, 2025 18:06
documentation/supported-tags.md Outdated Show resolved Hide resolved

Once a tag is no longer maintained, it will be considered unsupported, and will no longer be updated. Unsupported tags will continue to exist in the container registry to prevent breaking any references to it.
When a .NET version or an OS version reaches End-of-Life (EOL), its tags will no longer be supported.
Unsupported tags and images will continue to exist in MAR, but they will no longer recieve updates for any reason.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it worth mentioned they will be annotated as EOL?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At some point, yes. Should that be tracked by Add documentation for using lifecycle (EOL) annotations (#6014)?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, my next question is there value in completing the documentation before making this announcement given we will be calling attention to this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do think it could be useful to have something to point to in the announcement. e.g. "To check if an image is EOL, <do xyz> ..."

Co-authored-by: Matt Thalman <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-announcement An announcement is needed to discuss customer impact
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants