Path to .NET 6

[Anipik]

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.

Branches

We have moved 6.0 development to the release/6.0 branch. We will be releasing the first live release next month.
The main branch is now open for 7.0 work.

Milestones

The 6.0 milestone will only be used for critical and blocking issues which are required to complete feature work and make a high quality release. All other issues have been moved to 7.0.

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.

cc @ericstj @danmoseley

[danmoseley]

Changing perversely to Future milestone so it doesn't show up in a list of work remaining.

[GSPP]

I'd be curious what the burn-down chart looks like currently. Is it publicly accessible?

[danmoseley]

@GSPP not sure how useful it is to you, but this is the latest graph -- maybe @jeffschwMSFT has a version that goes back further.

You can see the steep drop to RC1 branching as we fixed/moved/closed issues, then it's been more steady since then as there are always incoming, etc. We are on track.

[danmoseley]

the thin line is issues marked 'blocking-release' -- which we're using to distinguish the must fix issues.

[jeffschwMSFT]

[GSPP]

That's cool to see. Thanks!