-
Notifications
You must be signed in to change notification settings - Fork 25.2k
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 Linux dev cert trust instructions #33221
Conversation
The dev experience should mostly match other platforms now, but I've added a section with caveats. Firefox no longer seems to need special handling on Windows or macOS. Is strongly suspect that section could also be removed in the pre-6.0 doc, but I haven't had a chance to confirm.
@Rick-Anderson besides your usual wordsmithing, I think I'll probably need some help with versioning. The functionality has been merged in 9.0 and is a candidate for backporting to 8.0, but 6.0 will probably still need the old instructions. So maybe we need to split the post-6.0 section (by copy-pasting?) and then update it (at least the Firefox instructions are outdated). |
One this merges I'll do another PR on versions. Normally we wouldn't mention what newer version can do, but in this case it's important because it's significant and motivation to update to .NET 9. The .NET 9 version won't mention it requires .NET 9 or higher, but I'd like to mention that in earlier versions. |
@Rick-Anderson The backport to 8.0 has been approved, so it will be in a patch but people on older versions of 8.0 won't have it. How do you want to reflect that in the docs (if at all)? |
Co-authored-by: Rick Anderson <[email protected]>
@Rick-Anderson Did I jump the gun on merging? I figured there was a publish step but it appears to be live. The new text won't be accurate until 9.0 RC1 and an 8.0 patch ship. |
Yes, I'll take care of that and let the 8.0 folks know what they need. Given .NET 8 is LTS, many customers are mandated to only deploy on LTS so that's important. |
@amcasey @Rick-Anderson I'm not sure of the best way to proceed here given all the PRs that have been done up to the point this was reverted, but I'm inclined to think the best way to start is by reverting the PR that reverted this PR and then looking to see what additional changes need to be done. Does that make sense to you? If we didn't do that we would have to salvage manually a lot of changes from this PR, wouldn't we? I don't know if there will be merge conflicts if I do revert the revert PR. |
The dev experience should mostly match other platforms now, but I've added a section with caveats.
Firefox no longer seems to need special handling on Windows or macOS. I strongly suspect that section could also be removed in the pre-6.0 doc, but I haven't had a chance to confirm.
Context: dotnet/aspnetcore#56582
Internal previews