Should we provide LTS-to-LTS migration documents?

[adegeo]

Describe the issue or suggestion

A customer recently contacted Microsoft recently asking about migration notes between LTS versions. While we do document version-to-version, we don't document LTS-to-LTS. Customers will choose LTS versions of .NET because of the long support guarantee. This customer in particular is tasked with upgrading production apps of various technologies (.NET MAUI, ASP.NET Core, etc) from .NET 6 to .NET 8. Providing migration details between LTS versions seems like a good thing to document.

Trying to follow the notes from .NET 6 to .NET 7, and then from .NET 7 to .NET 8, might be overwhelming and hard to follow. Also, consider that some may not even upgrade to .NET 8, even when support for .NET 6 ends. They may just upgrade when something breaks. In the future it could be possible that a customer is migrating from .NET 6 to .NET 10. Having to go through 6 -> 7 -> 8 -> 9 -> 10 release notes would be difficult. But with LTS-to-LTS they would just be going through 6 -> 8 -> 10 which is more manageable.

@gewarren @jamshedd

[AClerbois]

Thank you @adegeo for the follow up :-)

I think the migration through LTS is a good alternative :-)

[gewarren]

@adegeo When you say migration notes, do you mean the breaking change docs like these?