[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Network Management to extragear/network
From:       Ian Monroe <ian.monroe () gmail ! com>
Date:       2009-11-04 13:04:55
Message-ID: f680fec50911040504l2274f58byf49675f3b0964d6c () mail ! gmail ! com
[Download RAW message or body]

On Wed, Nov 4, 2009 at 5:38 AM, Sebastian Kügler <sebas@kde.org> wrote:
> On Wednesday 04 November 2009 11:54:30 Will Stephenson wrote:
>> I'd like to propose that the Network Management stack
>> (libs,knetworkmanager,plasmoid) moves to extragear/network in time for KDE
>> 4.4.  This way it's released but still has the schedule flexibility to
>>  react  to changes in NetworkManager and possibly other network management
>>  backend systems.
>
> The Plasmoid is not ready yet, and might not be in time for 4.4. It's also not easy
> to split off. I'd not build it for now so we don't have people accidentally using it
> and then wonder why it doesn't work. I hope I can get some substantial improvements
> in in time for 4.4, but there's a good chance that it won't be ready. Having the
> plasmoid separate would certainly not help development of it, but I'm happy with a
> separate review of this piece of code when the time comes. I hope people are OK with
> this modus operandi?

I miss why moving to extragear means splitting anything up? Also not
wanting to release with 4.4 and have some more flexibility is a good
reason to be part of extragear. Its the whole point.

We shouldn't give any rule exceptions though, moving to extragear
means a 2 week stay in kdereview.

Ian
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]