It is best not to think about v10 as a single huge release as we had historically, because we're in the process of switching to the new development model similar to the current Windows development model, with periodic feature rich updates. For example, we will deliver a big part of "v10" features in the upcoming 9.5 Update 3, then even more "v10" features in 9.5 Update 4, etc. So the build that will eventually carry "v10" version (if we even have versions still) may actually only add one or two remaining features, with the rest of the announced features already introduced in the previous updates.
The primary reason is that with the amount of features we're building at the same time these days (thanks to the development team size), it is really hard to time them to the given major release without having some features holding other for half a year or more due to varying feature complexity.
Another reason is that our legacy approach with fixed yearly release cycle really constrained our innovation and made it impossible to jump new cool ideas "on the fly". But the new approach will give us ability, for example, to add a few simple but very innovative features that we've just came up with recently, based on the feedback and some market shifts of the past months, right in the immediate updates.
Of course, we will see how is it going to work for us and our customers, and revise this new paradigm as needed. However, those of you who watched B&R development closely, probably noticed how we have been moving to this model in the past couple of years already, with every B&R update becoming more and more feature rich. This approach with periodic incremental enhancements was very well received by our customer base because it also helps from reliability perspective, by containing the introduced changes to only a part of the product functionality, by allowing us to quickly address pressing support issues with a public update, etc.