`main` is now .NET 11, use `release/10.0.1xx` for .NET 10 work!

[baronfel]

Hello all.

We're reaching the final stages of .NET 10's initial release development. We've branched release/10.0.1xx off of main as of a little while ago, which means that main is now logically .NET 11 (even though .NET 11 versioning activities haven't yet completed).

This means if you want something in .NET 10 at all, you need to make sure to either

• target the release/10.0.1xx branch as your base when making a PR, or
• continue to target main, but use the /backport to release/10.0.1xx command in your PR after it merges to trigger a backport

Commits to release/10.0.1xx will flow to main automatically as part of our standard forward-flow definitions for as long as .NET 10 is in support, as we do for all of our servicing development.

Thank you for your attention to this matter.

Cheat Sheet Table

Desired Release	Branch to target	Notes
.NET 11	main
.NET 10, RC1	release/10.0.1xx-rc1	you will need to manually backport fixes to release/10.0.1xx for RC2 and beyond
.NET 10, RC2 and beyond	release/10.0.1xx

[baronfel]

Closing this now as the announcement has served its purpose. Happy hacking on .NET 11 on main, folks!

[Youssef1313]

@baronfel Do you want to unpin the issue as well?