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

Path to .NET 6.0 for this repo #54569

Closed
danmoseley opened this issue Jun 22, 2021 · 4 comments
Closed

Path to .NET 6.0 for this repo #54569

danmoseley opened this issue Jun 22, 2021 · 4 comments

Comments

@danmoseley
Copy link
Member

It’s time to start looking ahead to ensure we have a smooth landing for our GA release in November! To do this predictably we progressively stabilize starting from this repo upwards. This process will very much like last year.

Milestones

We’ll shortly begin to pass through issues that haven’t been triaged yet, or that have their milestone set to 6.0. Our goal is that only issues that are must-fix for the release have the milestone set to 6.0. Note: if an issue has its milestone set to 6.0 that doesn’t necessarily mean it won’t get fixed for the 6.0 release. It means that the others need to get fixed first. In many cases we’d still take a PR for other fixes. By reducing the bugs set to 6.0 we make sure we focus on what we really need to fix to make a quality release.

Key dates in this repo

On July 13th feature work in this repo will stop. This is also the date we expect to snapshot the branch for our final preview release. There may be a few cases where feature work runs longer with special approval, but by this date we aim to be working only on final bug fixes.

On Aug 17th we aim to get to zero bugs in this repo for the 6.0 milestone. This is also the point where we move 6.0 development to its own branch. All code changes will continue to go into main, and we’ll cherry-pick into that branch just the critical ones we want to go out in .NET 6.0. What this means is that you, the community, can continue to work normally in main throughout.

How you can help

As always, we welcome any and all bug reports and pull requests We also ask for your understanding when we cannot fix something – and if you believe we mis-prioritized an issue, we welcome your feedback.

The above dates only apply to this repo: up-stack repos such as dotnet/aspnetcore and dotnet/winforms will run longer on their own schedules, but we will all release together in November.

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Jun 22, 2021
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@danmoseley danmoseley added area-Meta and removed untriaged New issue has not been triaged by the area owner labels Jun 22, 2021
@danmoseley danmoseley pinned this issue Jun 22, 2021
@jeffhandley jeffhandley added this to the 6.0.0 milestone Jul 13, 2021
@danmoseley
Copy link
Member Author

Thanks for all your help! Here's an update of how we're doing with bugs set to the 6.0 milestone. We have just over two weeks to get to zero before the branch for 7.0.

graph (Small)

@danmoseley
Copy link
Member Author

Your help is welcome! If you want to help root cause or fix any issues, take a look here:

https://issuesof.net/?q=is%3Aopen%20is%3Aissue%20repo%3Aruntime%20milestone%3A6.0.0

I've linked to @terrajobst handy app that allows querying across dotnet repos, and complex conditional operations with parentheses and operators.

@Anipik
Copy link
Contributor

Anipik commented Aug 19, 2021

closing in favour of #57770

@Anipik Anipik closed this as completed Aug 19, 2021
@Anipik Anipik unpinned this issue Aug 19, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Sep 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Development

No branches or pull requests

4 participants