[yast-devel] Nürnberg YaST team meeting 2008-11-25
present: mantel, schubi, dmacvicar, aschnell, sh, gs, shaas, snwint, tgoettlicher, ma, jdsn minutes: dmacvicar - biggest topic: how do we branch, when do we branch suggestion: branch a Code11 only, and branch again openSUSE/SLE only if required. linuxrc also follows this strategy - gs: fixing locking bug with rug -> locks are not matching certain packages. - libzypp: some issues with tribool usage in preferences/settings. - bnc#439802 WIP architecture change, rename and script requires bash, everything at the same time breaks installation order. - long discussion about non installed (satisfied) patterns/patches, and how they confuse users. - at least 4 bugs open about the topic - need to do something about it, either adapt the concept or the user interface - AI: remove fixed boost rps from prefered-rpms in cruisecontrol server. No longer needed (fixed boost is in factory) - dmacvicar has a patch for Qt 4.x tooltips, will send for review (not for 11.1) - PackageKit 0.3.11 was released, sreeves took that one. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Is there any (reasonable) output of that discussion, to let others know as well? I mean, the whole concept of patterns in user interface is ... somehow flawed, or better, no clear policies what is the correct behaviour supposed to be are defined (see also: https://bugzilla.novell.com/show_bug.cgi?id=437162#c9 and follow-up). At least, I've been unable to find any, maybe I just don't know where to look. And I'm not currently talking only about setting correct pattern status, but also about correct transitions between the states and propagating pattern status changes to related packages ('pattern content'). I'd be really happy if we finally got down to defining some reasonable concept we can stick to when it comes to patterns and UI. frozenB. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Is there any (reasonable) output of that discussion, to let others know as well? I mean, the whole concept of patterns in user interface is ... somehow flawed, or better, no clear policies what is the correct behaviour supposed to be are defined (see also: https://bugzilla.novell.com/show_bug.cgi?id=437162#c9 and follow-up). At least, I've been unable to find any, maybe I just don't know where to look. And I'm not currently talking only about setting correct pattern status, but also about correct transitions between the states and propagating pattern status changes to related packages ('pattern content'). I'd be really happy if we finally got down to defining some reasonable concept we can stick to when it comes to patterns and UI. frozenB. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (2)
-
Duncan Mac-Vicar Prett -
Katarina Machalkova