On 02/16/2011 09:12 PM, Karsten König wrote:
Heya,
11.4 is comming up quickly and there will be no general branch update for kde, so it's single bug fixing, they won't disappear by a sudden rush of changes anymore. The 11.4 release will probably see another increase again.
Don't be pessimistic 4.6 rocks :-)
So in the last meeting I raised a question how we could get better bug triage coverage especially validating bugs and finding possible upstream bug fixes.
Bille had the idea of dedicated bug search querries and people who will cover them to increase the chance to gain knowledge in this area, the best example might be kdepim, validating a range of kmail bugs to upstream reports will be faster then switching from an okular crash to a plasma graphical glitch to a power munching kded process.
That's a super cool idea the pre-made query : Bille just check if they can be shared, we tried that with bwiedermann, and they are stored in the bugzilla account (but was in November)
This would include a general splitting up into groups: pim, workspace, defaults, random-apps
sounds good to me.
Most important is finding out about upstream reports and possible patches, these save a ton of time and can be applied quickly, spotting regular reporters and inviting them into #opensuse-kde might be a good idea as well to get them about the team.
Finding upstream could be easy if we can emulate the crash report done by drkonqi Most of the bug I encounter during the factory 11.4 process goes directly upstream. My bad, is that I didn't open each time a novell one, only when I found that only opensuse people where impacted. Is that a good practice or not ?
There is a opensuse bug hunt on sunday http://news.opensuse.org/2011/02/16/open-bugs-day-on-sunday-the-20th-of- february/ It's 5 days before rc2 so it's a good time to find necessary upstream patches, test them in KDF and push to Factory before the deadline. (I'll have a very long saturday in Dresden so I hope I'll be fit to join)
Unfortunately, I will 11 hours stick on a plane seat direction to LA marketing fest, and presume I will not be behind a computer immediately. Hey but report is very welcome, a new organization about bug management is also marketing news :-)
On the other hand timely handling incoming bugs helps keeping the bugreporters reporting bugs and getting required information that's often forgotten (the usual log files for example) http://en.opensuse.org/openSUSE:Bug_Screening_KDE#Bugreport_organization_in_... explains a good way to screen the incoming stuff.
Yeap last year (in 1 and a half : osc09 ) I learned from Will that -debuginfo package doesn't eat cpu time (just disk place) They are really useful in case of crash. Explaining how to get them installed (drkonqi sometimes fail) is a piece of cake.
Any comments on the issue? Other ideas? Am I making a fuzz about a non- problem?
Certainly not .. We have some numbers we failed during the last months ( the infamous crash with nvidia 260 and 32 bits for example )
Regards, Karsten
-- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org