Recommended way for bigger changes in git ?

[David Faure]

On Thursday 19 April 2012 22:23:56 Alexander Neundorf wrote:
> AFAIK you don't want me to increase the version number of e-c-m, which
> would  handle this issue ?

On the contrary. Do update the version number, and the required version number 
in kdelibs frameworks.

The lack of required-version-increase *is* what broke my setup last time.

Because an old version is preferred over a newer version, when picking up ECM 
(as long as the old version is >= required version), what breaks is exactly 
that: making major changes without upgrading the version number.

Example:
Assume that kdelibs says "the required version is >= v3".
It means 'old v3' and 'new v3' both have to keep being supported, even if some 
major change went into 'new v3' and later on into 'v4'. Someone upgrading 
(with "git pull") directly from 'old v3' to 'v4' will end up without that 
change, and things will break if that change is in fact required.

It would just be simpler to pick the newest available version, rather than 
keep using an "old v3", just because "version must be >= v3"...

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Sponsored by Nokia to work on KDE, incl. KDE Frameworks 5