Mailinglist Archive: opensuse (3572 mails)

< Previous Next >
Re: [opensuse] openSUSE 11.0 and the Non-ready KDE4
  • From: "Rajko M." <rmatov101@xxxxxxxxxxx>
  • Date: Sat, 16 Feb 2008 11:19:56 -0600
  • Message-id: <200802161119.56932.rmatov101@xxxxxxxxxxx>
On Saturday 16 February 2008 10:05:39 am Monkey 9 wrote:
Which is the goal. Guys that work on debugging are usually very fast to
find duplicates and dismiss false report. Sometimes to fast on former,
IMHO, but if reporter can provide details they are pretty efficient.
 

Ofcourse, only i notice that on many bugreports, there is not going to
be any reaction.
Which rises the question on my side:  Why take the effort to make them,
if they are not intended to be fixed?

The bug fixing is not always simple.
Developer has to make sure that bugfix will be included upstream, to make sure
that is as little differences between openSUSE version and upstream one.
Sometimes one has to reiterate question/proposal because developer see
software from different prospective than user. Than when is all clear (both
reporter and developer talk the same language :-) ) there is their management
that has to give approval and also upstream project has to agree. Some
developers will take time to give you feedback, so you will know that they
work on the bug, others not. They will just work on the bug and for you as
reporter it seems that nothing is happening. So far I know there is no rule
to give feedback and each developer is handling that in his own way.

This is example of simple usability bug and, in my opinion, proper user
feedback. No many words, ie. time lost to keep reporter informed, but enough
to let me know that bug is in process and my report was not waste of time.
https://bugzilla.novell.com/show_bug.cgi?id=347423
and upstream discussion:
http://www.openoffice.org/issues/show_bug.cgi?id=5226

--
Regards, Rajko.
See http://en.opensuse.org/Portal
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
This Thread
Follow Ups