SameMajorVersionWithPreleases is intended implement the versioning
scheme followed by many KDE projects: minor releases after some high
number (eg: 90) are considered to be pre-releases of the next major
version, and are not compatible with the current major version. This
allows alpha and beta releases to be ordered correctly by
version-number-aware software like package managers (an alpha of version
2 should have a higher number than any release of version 1, but less
than version 2.0).

So a request for version 2.1.0 of a piece of software should not be
satisfied by 2.93.4, because that is actually a pre-release of version 3.
On the other hand, a request for version 2.91.0 should be satisfied
by version 3.1.0.

Note that prereleases are not considered unless explicitly requested, so
2.93.4 will not satisfy requests for version 3 (or version 2) of a piece
of software.

Testing Done

Unit tests pass.

Screenshots

Files

The next time KDE Frameworks will use such a numbering scheme is ... in a very long time, for KF6 :-)

But yeah, other software produced by the KDE community follows this versioning scheme too. So I agree with the need, I would just make the description more generic and talk about the habits of the KDE community, not just KDE Frameworks.