-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Add .NET major version release checklist #5034
Conversation
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's great to have this all described in one place.
.github/ISSUE_TEMPLATE/releases/dotnet-major-version-release.md
Outdated
Show resolved
Hide resolved
.github/ISSUE_TEMPLATE/releases/dotnet-major-version-release.md
Outdated
Show resolved
Hide resolved
.github/ISSUE_TEMPLATE/releases/dotnet-major-version-release.md
Outdated
Show resolved
Hide resolved
.github/ISSUE_TEMPLATE/releases/dotnet-major-version-release.md
Outdated
Show resolved
Hide resolved
.github/ISSUE_TEMPLATE/releases/dotnet-major-version-release.md
Outdated
Show resolved
Hide resolved
.github/ISSUE_TEMPLATE/releases/dotnet-major-version-release.md
Outdated
Show resolved
Hide resolved
.github/ISSUE_TEMPLATE/releases/dotnet-major-version-release.md
Outdated
Show resolved
Hide resolved
.github/ISSUE_TEMPLATE/releases/dotnet-major-version-release.md
Outdated
Show resolved
Hide resolved
- Example announcement: https://github.com/dotnet/dotnet-docker/discussions/4995 | ||
- [ ] Update documentation as necessary to reference the new .NET version | ||
|
||
## EOL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was not expecting this given the title. Should this be in a separate doc?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am fine with this going in a separate doc. It's pretty unlikely that we would forget when a major .NET version goes EOL, but I do see value in tracking the date on the board either way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO, I don't think EOL belongs in a separate doc. I don't see value in that. This is already a long-lived checklist covering alpha to GA so including EOL is just part of the overall lifecycle. The title of the doc could be changed to ".NET Version Lifecyle Checklist" or something.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If that's the case, this needs rewording File all issues at once when a new .NET version is in Alpha.
. IMO we shouldn't be opening an EOL issue until the EOL is known and closer to the EOL date. The presence of this issue sooner could cause confusion.
Fixes #4574
I will continue to update this as I work on #5005