.NET 6.0.2

[czdietrich]

Hi, I just wanted to ask kindly whether there is an expected timeframe for the next service pack of .NET (SDK)? I know there are no specific dates for releases but usually it's about once a month and the last one (6.0.1) was on Dec. 14th. I would not explicitly ask but .NET 6 introduced a hand full of regressions that are already fixed but not yet released which is a show stopper for the release of our application suite. So is there anything blocking the next release or is it already in the pipeline?

Best regards
Michael

[dotnet-issue-labeler]

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.

[ghost]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Hi, I just wanted to ask kindly whether there is an expected timeframe for the next service pack of .NET (SDK)? I know there are no specific dates for releases but usually it's about once a month and the last one (6.0.1) was on Dec. 14th. I would not explicitly ask but .NET 6 introduced a hand full of regressions that are already fixed but not yet released which is a show stopper for the release of our application suite. So is there anything blocking the next release or is it already in the pipeline?

Best regards
Michael

Author:	czdietrich
Assignees:	-
Labels:	area-Meta, untriaged
Milestone:	-

[danmoseley]

Hello @czdietrich . It is expected to ship in the 2nd Tuesday of February. We ship almost every month, but skip January because of the holidays.

Are there any issues you are encountering that you have not confirmed are fixed in it?

[czdietrich]

Hi @danmoseley, thank you for the quick response.
The both regressions I am referring to are a bug that created broken installers that is already merged and a bug in WPF that could lead to crashes that is currently about to be merged into .NET 6.0 servicing branch.

So, if these both are fixed then we are fine with our release. :)

[danmoseley]

The 6.0.2 build is already prepared , so that WPF fix would unfortunately not be in it. I am not familiar with it - perhaps there is a workaround? I am sorry to hear it is delaying your release.

[czdietrich]

Thank you for clarification. That the WPF bug won't be part of the upcoming .NET 6 servicing release is very unfortunate, since there seems to be no easy workaround for it, but waiting for a following servicing release is not an option, so we simply have to take it how it is at the moment.