Suggesting that QML use Semantic Versioning

When you upgrade versions of Qt and QML and then use those new kits in Qt Creator, it is surprising to me that I have to hunt around and discover the new (presumably better) versions of QML libraries.

Instead of

• QT 5.9 -> import QtQuick 2.9
• QT 5.8 -> import QtQuick 2.8
• QT 5.7 -> import QtQuick 2.7

Why can't I just do:

import QtQuick 2

and then get the latest, bug-fixed, backwards-compatible version of the QtQuick library?

http://semver.org/ solves this by giving a standardized meaning to release tags:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

Using this methodology, I can always get the latest, backwards compatible version of a library:
import QtQuick 2
and then, if I need to, I can peg it to a specific version number:
import QtQuick 2.7

Anyways, I am befuddled by the lack of consistent release number usage in the docs and the way I have to manually update libraries when I upgrade Qt versions.