I completely understand your frustration, John. We acknowledge that clearer communication on upgrade compatibility would have been helpful, and we’ll work to improve how we document these kinds of changes in future Developer Previews. While we can’t guarantee direct upgrades from early "L" builds to later preview versions, we’re looking into possible ways to mitigate this for future updates. Thanks for your feedback, and we truly appreciate your engagement!

Hi Andreas! We appreciate your enthusiasm! At this stage, the documentation is still in progress and will be updated as we finalize the release content.

If there are specific areas you're interested in testing, let us know, and we’ll do our best to provide some guidance.

Thanks for your patience!

Thank you for bringing this to our attention!

The upgrade issue arises from differences between early and later preview versions. Early preview versions were built from a branch that is always considered newer than other branches, which affects the upgrade path. As a result, upgrading from these early versions to later ones may encounter issues.

We recommend installing the latest preview version directly rather than upgrading from an earlier preview.

We apologize for any inconvenience this may cause and appreciate your understanding.

Thank you for pointing that out! The documentation links currently serve as placeholders and will be updated as we get closer to the final build and have more details to share. Since this is an early Developer Preview, some content is still in progress, and we’ll provide full documentation as features are finalized. We appreciate your patience and feedback during this phase!