On Tue, Aug 16, 2011 at 8:50 PM, Alan Alpert <[email protected]> wrote: > The advantages of the other approach is that we can be honest about the > version numbers. The major and minor version implications for Qt and QML have > diverged slightly, especially in the patch releases. A patch release for Qt > should not affect public C++ API, and this is entirely consistent with a new > minor release of QML (which can add new QML API, the QML versioning system > allows this to be safe).
Besides not affecting public C++ API I also don't think it's a good "behavior" to add features on a minor release. Minor releases are meant to fix stuff of the major release, that's why we call it patch releases :) Right now it only happened in Qt 4.7.4 and at least for my customers it caused a lot of confusion. If you don't think about Nokia (which only has good reasons to do this because of weird situations), I can't think about good reasons to add features on minor versions as everybody else is also waiting for the major release to get their features into Qt. Cheers, -- ------------------------------------------------------- Artur Duque de Souza openBossa INdT - Instituto Nokia de Tecnologia ------------------------------------------------------- Blog: http://blog.morpheuz.cc PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net ------------------------------------------------------- _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
