The case for a kdelibs 4.8
Albert Astals Cid
aacid at kde.org
Thu Sep 29 23:02:58 BST 2011
A Dijous, 29 de setembre de 2011, Kevin Kofler vàreu escriure:
> Albert Astals Cid wrote:
> > A Dijous, 29 de setembre de 2011, Kevin Kofler vàreu escriure:
> >> 1. This puts kdelibs 4 into maintenance mode even before KDE
> >> Frameworks 5 is anywhere near a release, let alone versions of the
> >> workspace and applications actually using it. As a result, we will
> >> fail to deliver new features to our end users for months if not
> >> years. And no, kdelibs features do not only target developers: Some
> >> application or workspace features require kdelibs changes, or in some
> >> cases, even consist of kdelibs changes only, e.g. my Plasma
> >> PackageKit integration work is entirely in kdelibs (libplasma).
> >
> > Please describe the features you need.
>
> https://git.reviewboard.kde.org/r/102175/
> https://git.reviewboard.kde.org/r/102291/
> https://git.reviewboard.kde.org/r/102350/
>
> The first one was merged into master after 4.7 branched and before it got
> frozen and is now in limbo there, the other 2 are stuck in ReviewBoard.
I'm not a plasma expert, but I'm almost sure you could argue these are bug
fixes :D And if you can not i don't think anyone is going to disagree on
putting that on 4.7 since it's seems to be a fairly small amount of code.
Albert
>
> > What you are describing is actually fine means that "old unmaintained"
> > libraries are still useful, so I do not see that it helps to prove your
> > point.
>
> It shows that they are useful, but that distributions have to patch them
> because upstream does not take fixes nor required system integration
> features anymore, which is not very helpful.
>
> Kevin Kofler
More information about the kde-core-devel
mailing list