The case for a kdelibs 4.8
Martin Gräßlin
mgraesslin at kde.org
Fri Sep 30 06:08:43 BST 2011
----- Ursprüngliche Mitteilung -----
> 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.
>
> > 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.
Have you actually tried to get the fedora patches into the 3.5 branch? I cannot remember any discussion about it on kcd...
Even if upstream would say no to the feautures what is wrong with doing a distro-3.5 branch so that at least all distros can have the same patches?
Cheers
Martin
>
> Kevin Kofler
>
More information about the kde-core-devel
mailing list