[kde-promo] Releasing Deprecated modules and Tier 4 Definition

[David Gil Oliva]

Hi!

El 26/03/2014 13:04, "Jos Poortvliet" <jospoortvliet at gmail.com> escribió:
>
> On Monday 17 March 2014 18:15:09 Kevin Ottens wrote:
> > Hello,
> >
> > Thanks for the feedback!
> >
> > Adding kde-promo in CC since it might have implications on future
> > communication.
>
> Ok, reading the whole thing - it seems a simple dot story would be useful
to
> explain that we've made some decisions that will be relevant for those
> porting their applications to Frameworks 5. If I understood it correctly,
> these decisions are:
>
> * Some major KDE technologies are deprecated and moved to KDE Porting Aids
> * KDE Porting Aids will have a limited shelf life of about three releases
> * List of tech to be in Porting aid not 100% finished but at least:
>  * khtml
>  * kjs
>  * kjsembed
>  * krunner
>  * kmediaplayer
>  * And of course it offers kdelibs4support (what is that exactly?)

>
> Also, these components are no longer part of KDE Frameworks 5, which you
want
> to emphasize in the communication.
>
> Just imagine what header would you like to see on an announcement/article:
> * Frameworks 5 To Not Include Deprecated Technologies
> * KDE Porting Aids To Have Three Releases
> * Introducing KDE Porting Aids And Changes to Frameworks 5
>
> I'm guessing the first, but - just checking.

I think that the third is more informative and more neutral.

Cheers,

David Gil

>
> /J
>
> > On Saturday 15 March 2014 16:59:54 Kevin Ottens wrote:
> > > Here are the different options, they're clearly not mutually
exclusive.
> > >
> > > 1) Split Tier 4 in a Tier 4 and a Tier Deprecated :)
> > > [...]
> > > 2) Release the deprecated content as a separate product
> > > [...]
> > > 3) Roll all the deprecated modules into KDE4Support
> > > [...]
> > > 4) Announce the deprecated modules will only be released three times
> > > [...]
> > >
> > > That's it for the four ideas to deal with the deprecated modules, now
> > > let's find a working cocktail.
> >
> > So let's pick the following cocktail: 1, 2 and 4.
> >
> > That means we immediately move khtml and kde4support out of KDE
> Frameworks
> > (to be widely advertised) and into a KDE Porting Aids product (to be
> > advertised only to existing KDE developers).
> >
> > Ben, I think you're going to hate me for that, but we learn as we
> > progress... That means we're moving ASAP khtml and kde4support
> > repositories out of the frameworks group of the projects tree into a new
> > portingaids group.
> >
> > We'll also announce at beta time the second product, and that we aim for
> > making only three releases out of it, coordinated with KDE Frameworks
> > releases as to give people time to port away from it.
> >
> > 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).
> >
> > I think that list makes sense. Is there anyone who couldn't sleep at
night
> > if those were in KDE Porting Aids?
> >
> > Regards.
>
> _______________________________________________
> Kde-frameworks-devel mailing list
> Kde-frameworks-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20140326/6b92c0c8/attachment-0001.html>