While there was no timeline given they definitely left us some hints that we can leverage to get a feel for how far along they are.
The Web2.0 has been in planning for quite a long time already. I recall having discussion with Greg about the next iteration of Web from at least three XDC's ago. That doesn't mean they had started it back then but they definitely were aware of the glaring issues of the Web1.0 and were trying to plan out a redesign.
Greg's keynote also hinted at where they are at as well. The fact that they could demo some of it and saying that it is considered a "priority" definitely puts it in the soon category. Also they showed the timeline of Web and where Web2.0 sits with the long running browser history. Xojo has indicated which browsers they are going to support and what functionality they are going to support which means they must be feeling pretty confident that they are on the downhill battle now to getting us at least something.
That "something" I think is the important part. It's possible for Xojo to get us access to Web2.0 without everything being complete. We don't need all the controls they announced in order to migrate our project. We just need all the existing controls to have their bootstrap equivalent to make the move over. We also don't need all the layout types to make the move either. From talking to Greg at XDC, it sounds like Auto-Layout could potentially come in a later iteration as it definitely isn't needed from the start. They also seemed open to feedback about potentially implementing other layout types, perhaps even a column based approach. Since bootstrap (and just about every other css layout library) already implements a column based design, it seems like there's a very real chance of this. It also could be easier to implement than AutoLayout. But even AutoLayout sounds like they have a good solution using Kiwi. (https://github.com/IjzerenHein/kiwi.js https://github.com/IjzerenHein/autolayout.js )
My guess is Xojo would love to get our hands on this as soon as they can. The sooner we can provide constructive feedback the better. And since all the new controls and layout styles aren't necessary in order to release 2.0 "soon" starts to sound even better. So the question remains what do they have left to do in order to get this in our hands.
Here are a few thoughts off the top of my head on what I think that could be:
The migration process from 1.0 to 2.0 probably will take a fair amount of work.
Getting IDE support and rendering the bootstrap controls will need to get done.
Finalizing how they want to handle (i.e. fix) WebStyles in the new framework.
Figuring out the WebControlWrapper for the new framework, I'm hoping to not have to completely rewrite all my controls.
Giving developers more leverage on controlling disconnects etc...
The good news is that the performance improvements of the new framework sounds amazing based on what Greg was saying. There are a ton of optimizations and there's lot more code running client-side. Moving to typescript has not only preemptively prevented new bugs but also found a bunch of previously unknown bugs (type-safety for the win!). It also sounds like the pace (similar to Android) is going pretty rapidly. Once you find the patterns the whole rinse and repeat thing makes it easier.