It doesn't in and by itself, but it signals a totally different approach to handling the software development cycles with a much less artificial "once-a-year-in-May" deadline. Since there are multiple opportunities to release features, there is less pressure to push possibly immature features out at the deadline.
It also shortens the QA cycle, not just the development cycle, so QA is more actively involved sooner and longer.
The proof of the pudding is in the eating so we'll see how it shakes out, and I'm sure there will be growing pains, but what they are doing reflects practices adopted by others that have proven to be successful.