> It's going to be released approximately in November

That's literally what I said, yes. The track record is very punctual so far, so "in the first half of November" is highly likely.

> the first RC is probably going to be released within the next few weeks

I made a statement about the way that things factually are at present. No less, no more. You characterised .NET 10 as a supported version, and this is not currently true.

> Now is the time to upgrade to 10, do some testing and then deploy once 10 is released.

Really "Now" ? or "probably within the next few weeks" when there's a version that is somewhat supported?

My employer is not in the habit of deploying 2 months after the work is done. Nor are they in the habit of prioritising this pre-release over other more important work. They love .NET LTS releases when they are releases, but absolutely will not put a pre-release on production, no matter if it's "supported" in some sense.

LTSs are for people or companies with low appetite for this kind of risk, or who have contractual obligations to not be running unsupported or pre-release software. Preview 7 is by definition not release quality yet, as it's not the release.

I expect .NET 10 to get picked up by my employer in the new year. This is based on my experience with the update to .NET 8

Your way does seem to better in that you have capacity to trial pre-releases, but the long release cycle sounds sucky.