Syncing ECM release number with KF5

Stephen Kelly steveire at
Thu Apr 2 11:29:18 BST 2015

> I have no particular objection,

So, what needs to be done to get this synced up? Bump the version in
the CMakeLists.txt and update some release-tarball-creating script?
David I guess the latter is for you?



On Fri, Mar 27, 2015 at 7:49 PM, Michael Palimaka <kensington at> wrote:
> On 28/03/15 03:48, Alex Merry wrote:
>> On Wednesday 25 March 2015 22:35:24 Stephen Kelly wrote:
>>> Hello,
>>> ECM release numbers are in sync with KF5 release numbers, except for the
>>> major component.
>>> This means that if you want to build the 5.x.y release you have to download
>>> the 1.x.y release of ECM. That doubles the complexity of your script which
>>> downloads the tarball to build it.
>>> That is bad and it is not necessary.
>>> Let's sync the major number for the next release.
>>> At some point the reason to make them out of sync was to be able to make ECM
>>> releases more frequently. That is very rare because KF5 releases are
>>> happening every month. If ECM needs to make an out of band release, it can
>>> use the 4th version number component.
>> I have no particular objection, although I think "doubling the complexity" of
>> scripts is overstating things a little.
>> Alex
> Is ECM actually part of KF5, or just happens to be released alongside
> it? (I thought the latter, hence the different version).
> FWIW the different version doesn't bother me at all as a downstream.
Kde-buildsystem mailing list
Kde-buildsystem at

More information about the kde-core-devel mailing list