Update branding to 8.0.0-alpha1

[dougbu]

No description provided.

[wtgodbe]

Do we need to update

aspnetcore/src/Framework/AspNetCoreAnalyzers/test/Verifiers/CSharpRouteHandlerCodeFixVerifier.cs

Line 68 in 2d953db

ReferenceAssemblies = ReferenceAssemblies.Net.Net70.AddAssemblies(ImmutableArray.Create(

?

[dougbu]

Do we need to update …

Shouldn't need to do that yet. Not changing any TFMs.

[wtgodbe]

Shouldn't need to do that yet. Not changing any TFMs.

Looks like the doc needs updating: #43308

[halter73]

Yeah. I think .NET 8 work should stay in feature branches for a while longer to avoid unnecessary merge conflicts.

[dougbu]

Yeah. I think .NET 8 work should stay in feature branches for a while longer to avoid unnecessary merge conflicts.

What's the context for your comment @halter73❔ We're not changing TFMs at this point but are changing assembly and package versions, along w/ all other .NET repos.

[ghost]

Hey @dotnet/aspnet-build, looks like this PR is something you want to take a look at.

[halter73]

I just don't want any big changes in main to cause merge conflicts with the .NET 7 release branches which I expect will be the more active source of changes over the next few weeks.

If we agreed to start .NET 8 branding this early, fine I guess. That shouldn't cause hard to resolve conflicts by itself, but I don't see the benefit to starting this early. When do we release 8.0.0-alpha1?

I expect life would be a whole lot easier for most devs if main only tracked .NET 7 changes for a little longer.

[dougbu]

Sorry, that's not the direction .NET has chosen at this time. We're rebranding now and in fact are late in doing so (due to test and infrastructure this hit yesterday).