Future frameworks releases

Eric Hameleers alien at slackware.com
Mon Jun 8 15:02:35 UTC 2015

On Tue, 9 Jun 2015, Michael Palimaka wrote:

> Date: Tue, 09 Jun 2015 00:25:24 +1000
> From: Michael Palimaka <kensington at gentoo.org>
> Reply-To: KDE release coordination <release-team at kde.org>
> To: release-team at kde.org
> Subject: Re: Future frameworks releases
> On 08/06/15 09:28, David Faure wrote:
>> Hello packagers,
>> The thread "Versioning of Frameworks" on kde-frameworks-devel has led to the
>> idea that some future frameworks (coming from the kdepim world) would not be
>> part of every Frameworks release, and would have their own versioning scheme.
>> This is at the request of their maintainer, Christian, CC'ed.
>> For example:
>>   KF 5.12 would contain KImap 2.1
>>   KF 5.13 would not contain a KImap release
>>   KF 5.14 would contain KImap 2.1.1
>>   KF 5.15 would contain KImap 2.2
> Why? Will other frameworks skip a release too if they have no commits?

The only sane way forward is that every Frameworks release contains 
all Frameworks tarballs, regardless of updates since the previous 
public release. Every Framework should adhere to the overall version 
This is the base on which you are building everything, guys! Don't 
start messing with tarballs present yes/no/perhaps and version number 

In the past everybody was very critical about when a piece of software 
was finally allowed to enter the holy ground of Frameworks, and with 
good reason: quality and stability. So please don't make us drift into 
a swamp by approving this KImap proposal.

Cheers, Eric

Eric Hameleers <alien at slackware.com>
Home: http://alien.slackbook.org/blog/

More information about the release-team mailing list