From : Brandon Jones < : Brandon Jones < bajones@google.com



Message-ID : <CAEGwwi3rfm0Z1kE2D2saEoNi0wy3Jpyk1BP31Uyk5Tn1f4_S3A@mail.gmail.com>

To : public-immersive-web-wg@w3.org, public-immersive-web@w3.org



Hey everyone! The last PRs for the "June" (ha ha) milestone were merged at the beginning of this week. This means that, according to our project doc <https://github.com/immersive-web/administrivia/blob/master/project.md> *we've now hit "VR Complete!"* [Celebratory image removed to appease the mailserver's attachment size limits] Congratulations to the entire Working Group for reaching this important milestone, and our sincerest thanks to everyone who has contributed to the spec in ways big and small! This has truly been a community effort. So what exactly does "VR complete" mean and what happens next? At this point the portions of the API dealing with core VR functionality (essentially: anything needed to replace WebVR) are "locked in". Unless we encounter major issues affecting the API's usability or security from this point forward we will be doing everything we can to avoid breaking backwards compatibility. We want browser vendors to feel secure in implementing the API and developers to feel confident that they can start creating content with it without the rug being pulled out from under them, and that starts *today!* That doesn't mean we're done, of course! There's still plenty of room for improvement in the spec, and we expect that we'll continue to tweak the behavior under the hood in ways that don't have major impact on applications using it for the sake of consistency, security, and clarity. There will be plenty of work to keep us busy right up through TPAC and beyond! Also, please note that in the current editors draft <https://immersive-web.github.io/webxr/> there are a couple of sections still marked "unstable", specifically the "immersive-ar" mode and the "XRRay" interface. These are *not* considered to be part of the VR complete stability milestone, since they are AR-focused. We will be breaking those out into a separate module over the next couple of weeks to allow work to continue on them in parallel while we finish up the "core" spec. Also, for the sake of avoiding confusion we'll be waiting until the modules split has been completed to cut the next Working Draft. Thank you again for everyone's support! --The Immersive Web Leadership Team