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? That said, the other components are good to go into 4.4. They're being released by at least two distros in their standard install and Will has been fixing bugs left and right to make it solid. > Does anyone disagree with this? I think it's a good idea. Maybe kdebase is even a better (I consider connecting to networks basic functionality), but as you note, upstream (networkmanager, connman, wicd, ...) might require intermediate releases. We could probably still do those, even if we end up in kdebase, of course. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 _______________________________________________ kde-networkmanager mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-networkmanager
