No ETA yet, sorry.
We are taking an inventory at the moment. This should give us a list of features and functions not yet in CL vNext, things I might have overseen (or ignored ;-) ). We will then decide what to do about these things and consult our current users.
We are also preparing a list of new features that we then can provide for voting to our users. This will be the base of the 2021 roadmap.
In the meantime, we are preparing the migration from the old to the new system:
- Prepare a tutorial for moving to vNext (for new and existing users)
- Setup the old API on the new system (so add-ons can keep working)
- Auto-convert logs to vNext (for users' convenience)
- Switch the URLs of the apps so vNext is the default
- Take a snapshot of the old system and switch it to read-only
To be honest, I am using vNext productively for more than a year now. And if it were not for reasons of usability and ease of transition, I would make the switch immediately.
We want to make the experience for all users as smooth as possible.
With limited resources available this takes time.
We started by advertising the new version in a banner on the old version.
More and more users are currently trying vNext.
We now eagerly await users' feedback on vNext.