Yes, he did. I did wonder about that. I thought it might have been a typo, but it can't be because the thing he mentioned wasn't fixed in 1.1.2 so it must be fixed in a yet unreleased version.
Which, I have to say, does (and this is the first time I've ever expressed any negativity towards anything here) annoy me slightly because if the developers are well aware of a vague roadmap which contradicts the one we're already aware of (i.e. 1.1.3 will be followed by 1.2) then I feel they should have been more vocal about that.
There's one thing keeping cards close to your chest when you're not aware of any changes to the official statement you've already given, but when they know they're definitely going to contradict the expectation they've set, it is somewhat disappointing.