• Mary Jo Foley: There’s a reason why MS is starting to test Win10 20H1 so early… and, no, it isn’t because they’re switching to annual releases

    Crestfallen.

    Yesterday, Mary Jo Foley published a report relying on her sources inside Microsoft about the surprising “Skip ahead” testing of Win10 20H1 — the version that isn’t due out until a year from now.

    I had speculated that, maybe, somebody inside Microsoft had come to their senses, and they were using this as a way to move to once-a-year versions of Win10. Nope. At least, according to Foley’s sources:

    Some people wondered if this was a sign Microsoft might be moving to one Windows 10 feature update per year (nope).

    Crestfallen, I tell you. She has a plausible reason:

    The Windows team is close to finalizing Windows 10 19H1. If schedules had all aligned, the core OS team would already be well on its way to finishing the new core platform release (codenamed “Vanadium”), targeted for internal delivery by June 2019, which would be the base of the next Windows 10 release [version 19H2 or 1909]. But the timing just doesn’t work out. As a result, my contacts say, the new plan is for the core OS team to skip its internal June platform release and just focus on the December 2019 internal release (codenamed “Vibranium”) — which will be the basis for the Windows 10 20H1 release.

    Which makes me want to curl up and suck on my thumb.

    It seems that the Azure tail is now wagging the Win10 dog.