What if we implement a feature similar to how cmake policies work? Instead of checking what runtime Qbs version we are running on, we check the version that is requested by the project.
So users that really don’t want to bother can stick to some old version and call it a day. This probably doesn’t make sense for every change like removing module properties and such (however is still useful for determining the default value) but for huge language changes does. The only question is how deep down do we want to support legacy code; maybe we can drop it every major version which we can release more often, say every 10 minor versions? Ivan >>> I'd like to point out two upcoming behavior changes. _______________________________________________ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
