Re: Releasing Deprecated modules and Tier 4 Definition

On Tue, Mar 18, 2014 at 4:36 AM, Markus Slopianka <[email protected]> wrote:

> On Monday 17 March 2014 18:15:09 Kevin Ottens wrote:
>
> > Now, the last point... What else do we want to move from KDE Frameworks
> to
> > KDE Porting Aids? Aleix and Aaron proposed the following content for KDE
> > Porting Aids:
> >  * kde4support (obvious);
> >  * khtml (planned for a long time);
> >  * kjs (because of khtml I gather);
> >  * kjsembed (ditto);
> >  * krunner (because of upcoming sprinter, and only one user anyway);
> >  * kmediaplayer (unused AFAIK).
>
> Um, isn't KDEWebKit missing? Digia already deprecated QtWebKit in favor of
> Chromium's Blink. Unless anybody is interested in maintaining QtWebKit the
> KDE
> bindings should be deprecated as well. Don't you think?
>
> _______________________________________________
> This message is from the kde-promo mailing list.
>
> Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set
> digest on or temporarily stop your subscription.
>

Maybe coming up with the list of modules now is not the most useful thing
now.
Can we maybe agree that we want an extra value in the <framework>.yaml file
indicating the maturity of the project?

A final list could be polished during the KF5 sprint [1].
Aleix

[1] https://sprints.kde.org/sprint/224


_______________________________________________
This message is from the kde-promo mailing list.

Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription.