KDE Frameworks Release Cycle

[Martin Klapetek]

On Sun, May 4, 2014 at 6:36 PM, David Faure <faure at kde.org> wrote:

> [Cross posting against my will...]
>
> On Sunday 04 May 2014 16:27:44 Luigi Toscano wrote:
> > I understand that the big concern was about the testing: stable branches
> did
> > not receive the same attention
>
> This is not the main concern.
>
> My main concern is that application developers prefer to work around bugs
> in
> KF5 (previously: kdelibs) rather than fix things at the right level,
> because
> "fixes in KF5 will only be available in 6 months, and I want the bug fixed
> now".
>
> Your suggestion (6-months "stable" release) brings us back to exactly that.
>
> We'd like to try something better. Monthly small increments.
> Never "big" changes that break things, they get cut into small increments
> too.
> So no reason to buffer changes for 6 months.
>

However this highly depends on the distro policies - if some of the big
distros say "we will not update KF5 every month because our policies", then
the 6 months buffer is just moved elsewhere, at the distro level because
they will update only with the new release. If the application makes a hard
requirement on some specific version (which would be the point of this),
then distros would not package that fixed app before there would be that
particular version of KF5, so I imagine the app developers would still work
around the bugs in their own code and release a minor version which the
distro would package. Or worse there would be patches at distro level.

Imho distributions' opinion should be highly taken into consideration
because these are the people actually delivering our code to 98% of users.

I like the original proposal, but I also think we need to stay pragmatic
and work with real world facts.

Cheers
-- 
Martin Klapetek | KDE Developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20140505/b7f29d9c/attachment.html>