On Friday 30 September 2011 22:19:40 Sven Burmeister wrote:
> Am Freitag, 30. September 2011, 17:12:01 schrieb Martin Gräßlin:
> > The bugtracker in it's current state does not help to increase the quality
> > of the software. In fact the quality decreases as the developers have to
> > spend time o
I think we are acting like it all has to be done manually which is
simply not true. Why are we tackling bug triage as something that only
a human can do? Computers are good a repetitive tasks. A little bit of
intelligent use of technology would reduce the "burden" on all of our
developers. KDE has
On Friday, September 30, 2011 09:10:22 PM Andras Mantia wrote:
> I agree. There is a common complaint by developers, that they waste
> their time on bug report reading/asnwering instead of coding. While this
> seems reasonable, you have to understand that developing a software
> product involve
>On 30 September 2011 14:44, Dr.-Ing. Edgar Alwers wrote:
> On Fri, 30 Sep 2011 15:59:45 +0200
> Myriam Schweingruber wrote:
>
>> I am answering here as an active bug triager.
>
> Sorry for the noise, bu you seem to be a "german language" native. What
> exactly is "triage" ? I could not find it
Am Freitag, 30. September 2011, 17:12:01 schrieb Martin Gräßlin:
> The bugtracker in it's current state does not help to increase the quality
> of the software. In fact the quality decreases as the developers have to
> spend time on managing garbage. Yes what we get is garbage. Most of the
> report
Hi Edgar,
on Friday 30 September 2011 20:44:23 Dr.-Ing. Edgar Alwers wrote:
> On Fri, 30 Sep 2011 15:59:45 +0200
>
> Myriam Schweingruber wrote:
> > I am answering here as an active bug triager.
>
> Sorry for the noise, bu you seem to be a "german language" native.
Good guess.
> What
> exact
On Fri, Sep 30, 2011 at 5:33 PM, Rui Maciel wrote:
> On 09/30/2011 01:29 PM, todd rme wrote:
>>
>> I don't think any of those are good options, since all of them have
>> the same result: spamming developers with huge amounts of useless
>> information. This would only make it far more difficult to
Henrik Kraft writes:
> I liked very much the KDE game kwrdclock and saw that is is no longer
> part of the debian distribution squeeze. As I tried to compile it from
> source some errors occured:
> - file about.moc could not be build
> - also the file applet.moc could not be build
> both files
On Fri, 30 Sep 2011 15:59:45 +0200
Myriam Schweingruber wrote:
> I am answering here as an active bug triager.
Sorry for the noise, bu you seem to be a "german language" native. What exactly
is "triage" ? I could not find it in my english dictionary ( is a little old )
Thanks for the explanatio
On Friday, September 30, 2011 16:33:36 Rui Maciel wrote:
> On 09/30/2011 01:29 PM, todd rme wrote:
> > I don't think any of those are good options, since all of them have
> > the same result: spamming developers with huge amounts of useless
> > information. This would only make it far more difficu
On 09/30/2011 01:29 PM, todd rme wrote:
I don't think any of those are good options, since all of them have
the same result: spamming developers with huge amounts of useless
information. This would only make it far more difficult to manage bug
reports. Just being patient seems like the only sol
Dear Sirs,
I liked very much the KDE game kwrdclock and saw that is is no longer
part of the debian distribution squeeze. As I tried to compile it from
source some errors occured:
- file about.moc could not be build
- also the file applet.moc could not be build
both files where missing.
kin
On Friday, September 30, 2011 14:26:22 Rui Maciel wrote:
> After all, if not here then how would we tackle this issue?
that's a great question, and it has a very simple answer that is a bit more
difficult to implement than it might at first seem, though it is completely
possible to accomplish:
On Friday 30 September 2011 09:44:54 Scott Kitterman wrote:
> Having fewer users or fewer bugs would help, so it may be that making the
> software either better or worse would reduce the bug triage backlog.
Sorry to disagree, in KWin we see the opposite. The better we become the bigger
the (usele
On Fri, Sep 30, 2011 at 15:09, Ian Wadham wrote:
> Resending. Sorry, I used the wrong sending address before and got bounced.
>
>...
> Surely there is some kind of database app behind bugzilla? Would it not
> be possible to produce reports and summaries that highlight and prioritise
> bugs accor
Hi Sven,
I am answering here as an active bug triager. Disclaimer: I am not a developer.
On Fri, Sep 30, 2011 at 11:56, Sven Burmeister wrote:
> Am Donnerstag, 29. September 2011, 13:25:49 schrieb Sebastian Kügler:
...
>
> So IMHO if you want good bug reports you have to start giving good feedba
On Friday, September 30, 2011 02:29:47 PM todd rme wrote:
> On Fri, Sep 30, 2011 at 11:56 AM, Sven Burmeister
>
> wrote:
> > Am Donnerstag, 29. September 2011, 13:25:49 schrieb Sebastian Kügler:
> >> > It's frustrating for users submitting bug reports when an easily
> >> > reproducible bug sits i
On Thursday, September 29, 2011 21:45:54 José Expósito wrote:
> is save in disk... But I'm stucked because the configuration is
> correctly saved on disk, but the signal is never emmited :S
it seems that this signal is only emitted if there is a X-KDE-ParentComponents
in the module's .desktop file
Le Vendredi 30 de septembre 2011 11:56:55 Sven Burmeister a écrit :
> Ok, so if a user reports a bug and gets no answer for weeks, what should he
> do? Keep posting to the bug every few weeks, blog about it, private email to
> the dev, ask on IRC (which would not be much different than a mailinglis
On 09/30/2011 01:29 PM, todd rme wrote:
I don't think any of those are good options, since all of them have
the same result: spamming developers with huge amounts of useless
information. This would only make it far more difficult to manage bug
reports. Just being patient seems like the only sol
On 09/29/2011 12:25 PM, Sebastian Kügler wrote:
This posting of bugreports to mailinglists is often seen as unnecessary, and
unfair since you're bringing attention to your pet bugs, which disadvantages
others' pet bugs.
As a user who filed a considerable number of bugs along the years, I
have
Resending. Sorry, I used the wrong sending address before and got bounced.
On 30/09/2011, at 10:29 PM, todd rme wrote:
> On Fri, Sep 30, 2011 at 11:56 AM, Sven Burmeister
> wrote:
>> Am Donnerstag, 29. September 2011, 13:25:49 schrieb Sebastian Kügler:
It's frustrating for users submitting
Am 30.09.2011 14:29, schrieb todd rme:
> On Fri, Sep 30, 2011 at 11:56 AM, Sven Burmeister
> wrote:
>> Am Donnerstag, 29. September 2011, 13:25:49 schrieb Sebastian Kügler:
It's frustrating for users submitting bug reports when an easily
reproducible bug sits in the queue, without even
On Fri, Sep 30, 2011 at 11:56 AM, Sven Burmeister
wrote:
> Am Donnerstag, 29. September 2011, 13:25:49 schrieb Sebastian Kügler:
>> > It's frustrating for users submitting bug reports when an easily
>> > reproducible bug sits in the queue, without even a comment, for six
>>
>> > months. For the r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/29/2011 11:48 AM, Sune Vuorela wrote:
> Many bug reports are 'low quality', as in 'hard to figure out what
> the submitter means'. There are really many bug reports in
> general. This leads to a fact that finding the 'high quality' bug
> reports
Am Donnerstag, 29. September 2011, 13:25:49 schrieb Sebastian Kügler:
> > It's frustrating for users submitting bug reports when an easily
> > reproducible bug sits in the queue, without even a comment, for six
>
> > months. For the record, I'm referring to this bug report here:
> This posting of
26 matches
Mail list logo
