networkmanager plasmoid SRU

Antonio Augusto (Mancha) mkhaos7 at
Mon Apr 27 19:35:54 BST 2009

On Mon, Apr 27, 2009 at 15:26, Harald Sitter <apachelogger at> wrote:
> On Montag, 27. April 2009 20:12:37 Antonio Augusto (Mancha) wrote:
>> On Mon, Apr 27, 2009 at 15:09, Harald Sitter <apachelogger at>
> wrote:
>> > Hola!
>> >
>> > Almighty sebas just suggested that we might push a more recent SVN
>> > snapshot of the nm plasmoid to jaunty-updates (seeing as it is a main
>> > package and horribly broken, but SVN ought to be in better shape...).
>> > Which IMHO is a very good idea, though we should apply a longer testing
>> > phase and do a more public call for testing in order to ensure that there
>> > are close to no regressions.
>> >
>> > Note that this also helps upstream mature the product, while the users
>> > get a more usable version right away. So, everyone wins, as long as we
>> > keep a tight QA on the SRU at least.
>> >
>> > Opinions? Volunteers?
>> While I'm experiencing no problem with the NM plasmoid I thing this a
>> good idea and I volunteer to test it.
>> Maybe this is a good kind of thing can already be pushed to the new
>> repos Johnatan is planning?
> We could keep rolling updates in the experimental section of the PPA
> reorganization, but in general I'd like to get that update to jaunty-updates
> itself in order to get the greatest rate of distribution amongst the users.
> A rolling update in experimental might actually help upstream track issues
> down without having to ask users to install the plasmoid from SVN. Though,
> someone would need to maintain that ;-)

While I agree that jaunty-updates would give the gratest distribution
rate, I don't agree with putting it there before doing a more
restricted test.
Thats why we have the experimental repos. Specially SVN stuff
shouldn't go there right of the bat.


More information about the kubuntu-devel mailing list