No, the statement says that there will be frequent breaking APIs, it doesn't make any claim about release strategy. Releasing breaking changes on every 0.minor release perfectly fits in this definition.

Making a quick judgement based on an assumption that's provably wrong isn't really the definition of a professional engineer.