Main branch net10.0 transition status tracking

[marcpopMSFT]

Current state

• main branch
  • partially open
  • Unable to take runtime flows or watch fixes
• 9.0.1xx
  • open for most changes.
  • High risk or breaking changes should wait for main.
  • 9.0.2xx will be created when RC2 branches the week of 9/16

main branch has been rebranded to 10.0.100-alpha but only has a net10 windows desktop runtime.
Some watch tests and template tests have been temporarily disabled.

Process
https://github.com/dotnet/sdk/blob/main/documentation/general/UpdateToNewTargetFramework.md

• Update branding (complete)
• Add net10 framework references (complete)
• Flow net10 runtimes <-- we are here
• Update global.json
• Retarget the sdk to net10.0
• Retarget default templates to target net10.0
• Unwind any changes made during the transition (as tracked below)

The history of changes we've made so far:

• Alpha Branding #42743
  • pin template versions
  • https://github.com/dotnet/sdk/issues/
  • disable format source build tests
  • Disable Tests Failing Due to Initial net10.0 Branding #42850

[WeihanLi]

Have a question about the target framework, currently, the SDK supports net8, would the SDK drop the support? Since net10 may conflict between net10.0 and netfx 1.0

[huoyaoyuan]

Since net10 may conflict between net10.0 and netfx 1.0

I think we will keep compatibility and force the usage of net10.0 instead of net10. This was mentioned in the initial TFM design:
https://github.com/dotnet/designs/blob/main/accepted/2020/net5/net5.md#what-about-net-10