Hi, have you considered a date-based versioning scheme? It would have practically the same features as the proposed one, but additionally carries the information how old a particular Qt Creator version is.
Cheers Dmitriy On Wed, Mar 24, 2021 at 10:06 AM Eike Ziller <eike.zil...@qt.io> wrote: > We want to switch Qt Creator to semantic versioning, which means bumping > the major version for each feature release, since we don’t keep binary > compatibility between these. > > - Next release after 4.15 is Qt Creator 5. > - Followed by Qt Creator 6 in December 2021. > - Qt Creator 7 in spring 2022 > - and so on. > > The major version of Qt Creator doesn’t have any meaning at the moment, so > we’d like to give it one. We almost always do incremental changes instead > of major overhauls in one go, so basing the major version on some kind of > feature change doesn’t make much sense. Bumping the major version for each > feature release sounds more sensible because of this, and fits the semantic > versioning scheme. > > Bump version to 5.0 beta1 (Id8510dd7) · Gerrit Code Review > https://codereview.qt-project.org/c/qt-creator/qt-creator/+/339992 > > changes the version used in the master branch. > > Br, Eike > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://qt.io > Geschäftsführer: Mika Pälsi, > Juha Varelius, Jouni Lintunen > Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht > Charlottenburg, HRB 144331 B > > _______________________________________________ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator >
_______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
