On 27.02.2018 22:06, Boudewijn Rempt wrote:
On Tuesday, 27 February 2018 20:39:31 CET Elvis Angelaccio wrote:
Exactly. Also, what Luca said: unconfirmed gives the impression that we
don't care about the bug.
My point is that confirmed/unconfirmed adds more problems than it solves.
Note _agai
On Wed, Feb 28, 2018 at 8:37 AM, Elvis Angelaccio
wrote:
> On martedì 27 febbraio 2018 16:08:44 CET, Ben Cooksley wrote:
>>
>> On Tue, Feb 27, 2018 at 11:32 PM, Elvis Angelaccio
>> wrote:
>>>
>>> Hi,
>>
>>
>> Hi Elvis,
>>
>>> recently we introduced a policy change in bugzilla and now every user h
On Dienstag, 27. Februar 2018 23:56:57 CET Boudewijn Rempt wrote:
> On Tuesday, 27 February 2018 23:17:02 CET Elvis Angelaccio wrote:
> > On martedì 27 febbraio 2018 21:06:04 CET, Boudewijn Rempt wrote:
> > > On Tuesday, 27 February 2018 20:39:31 CET Elvis Angelaccio wrote:
> > >> Exactly. Also, w
Il 27 febbraio 2018 20:06:04 GMT+00:00, Boudewijn Rempt ha
scritto:
>On Tuesday, 27 February 2018 20:39:31 CET Elvis Angelaccio wrote:
>
>> Exactly. Also, what Luca said: unconfirmed gives the impression that
>we
>> don't care about the bug.
>>
>> My point is that confirmed/unconfirmed adds more
On Tuesday, 27 February 2018 23:17:02 CET Elvis Angelaccio wrote:
> On martedì 27 febbraio 2018 21:06:04 CET, Boudewijn Rempt wrote:
> > On Tuesday, 27 February 2018 20:39:31 CET Elvis Angelaccio wrote:
> >> Exactly. Also, what Luca said: unconfirmed gives the impression that we
> >> don't care abo
On martedì 27 febbraio 2018 21:06:04 CET, Boudewijn Rempt wrote:
On Tuesday, 27 February 2018 20:39:31 CET Elvis Angelaccio wrote:
Exactly. Also, what Luca said: unconfirmed gives the impression that we
don't care about the bug.
My point is that confirmed/unconfirmed adds more problems than it
On Tuesday, 27 February 2018 22:52:16 CET Elvis Angelaccio wrote:
> On martedì 27 febbraio 2018 21:09:12 CET, Boudewijn Rempt wrote:
> > On Tuesday, 27 February 2018 20:33:37 CET Elvis Angelaccio wrote:
> >> It's confusing also for new developers/triagers. Yesterday a new triager
> >> asked me why
On martedì 27 febbraio 2018 21:09:12 CET, Boudewijn Rempt wrote:
On Tuesday, 27 February 2018 20:33:37 CET Elvis Angelaccio wrote:
It's confusing also for new developers/triagers. Yesterday a new triager
asked me why I had not set a reproducible bug as confirmed and when he
should set the confi
On Tuesday, 27 February 2018 20:29:07 CET Martin Flöser wrote:
> For KWin at least I would not need the destinction. Every bug is looked
> at in less than 24 hours. On the other hand no bug is reproduced till I
> try to fix it. And that can take time, sometimes years, sometimes never.
Then you pr
On Tuesday, 27 February 2018 20:33:37 CET Elvis Angelaccio wrote:
> It's confusing also for new developers/triagers. Yesterday a new triager
> asked me why I had not set a reproducible bug as confirmed and when he
> should set the confirmed status. It's just an unnecessary step which makes
> the w
On Tuesday, 27 February 2018 20:39:31 CET Elvis Angelaccio wrote:
> Exactly. Also, what Luca said: unconfirmed gives the impression that we
> don't care about the bug.
>
> My point is that confirmed/unconfirmed adds more problems than it solves.
Note _again_ that I am NOT asking for keeping unco
On martedì 27 febbraio 2018 20:19:24 CET, Martin Flöser wrote:
Am 2018-02-27 13:43, schrieb Boudewijn Rempt:
On Tuesday, 27 February 2018 13:30:12 CET Paul Brown wrote:
Is it true that users get confused by the bugtracking system?
If so, this is
an issue, right?
Well, users can get confused
On martedì 27 febbraio 2018 16:08:44 CET, Ben Cooksley wrote:
On Tue, Feb 27, 2018 at 11:32 PM, Elvis Angelaccio
wrote:
Hi,
Hi Elvis,
recently we introduced a policy change in bugzilla and now every user has
the power to change the status of any ticket.
This is good (and consistent with ph
On martedì 27 febbraio 2018 11:41:04 CET, Boudewijn Rempt wrote:
On Tuesday, 27 February 2018 11:32:10 CET Elvis Angelaccio wrote:
Hi,
recently we introduced a policy change in bugzilla and now every user has
the power to change the status of any ticket.
This is good (and consistent with phabri
Am 2018-02-27 20:22, schrieb Boudewijn Rempt:
On Tuesday, 27 February 2018 20:19:24 CET Martin Flöser wrote:
Am 2018-02-27 13:43, schrieb Boudewijn Rempt:
> On Tuesday, 27 February 2018 13:30:12 CET Paul Brown wrote:
>> Is it true that users get confused by the bugtracking system? If so,
>> this
Am 2018-02-27 20:21, schrieb Boudewijn Rempt:
On Tuesday, 27 February 2018 20:15:40 CET Martin Flöser wrote:
As KWin has the same problem as Krita I can also answer. In the case
of
KWin about 90 % of the incoming bug reports is not a bug, but either
duplicate, driver crash, useless crash rep
On Tuesday, 27 February 2018 20:19:24 CET Martin Flöser wrote:
> Am 2018-02-27 13:43, schrieb Boudewijn Rempt:
> > On Tuesday, 27 February 2018 13:30:12 CET Paul Brown wrote:
> >> Is it true that users get confused by the bugtracking system? If so,
> >> this is
> >> an issue, right?
> >
> > Well,
On Tuesday, 27 February 2018 20:15:40 CET Martin Flöser wrote:
>
> As KWin has the same problem as Krita I can also answer. In the case of
> KWin about 90 % of the incoming bug reports is not a bug, but either
> duplicate, driver crash, useless crash reports from Arch users or user
> support ques
Am 2018-02-27 14:45, schrieb Paul Brown:
On Tuesday, 27 February 2018 13:43:17 CET Boudewijn Rempt wrote:
On Tuesday, 27 February 2018 13:30:12 CET Paul Brown wrote:
> Is it true that users get confused by the bugtracking system? If so, this
> is an issue, right?
Well, users can get confused by
Am 2018-02-27 13:43, schrieb Boudewijn Rempt:
On Tuesday, 27 February 2018 13:30:12 CET Paul Brown wrote:
Is it true that users get confused by the bugtracking system? If so,
this is
an issue, right?
Well, users can get confused by _everything_. Though I probably have
more
absolutely non-te
Am 2018-02-27 12:22, schrieb Paul Brown:
On Tuesday, 27 February 2018 11:51:42 CET Boudewijn Rempt wrote:
On Tuesday, 27 February 2018 11:47:22 CET Paul Brown wrote:
> On Tuesday, 27 February 2018 11:41:04 CET Boudewijn Rempt wrote:
> > Given that bugzilla is a tool for developers, I don't care
On Tue, Feb 27, 2018 at 11:32 PM, Elvis Angelaccio
wrote:
> Hi,
Hi Elvis,
> recently we introduced a policy change in bugzilla and now every user has
> the power to change the status of any ticket.
>
> This is good (and consistent with phabricator) but there is a big downside:
> many people will
On Tuesday, 27 February 2018 15:03:02 CET Ilmari Lauhakangas wrote:
> I don't think it's relevant to ask Boud to start some huge Bugzilla user
> experience revamp on top of the things he is already dealing with.
Sorry for the confusion. I was using the royal "you", that is, referring to
"everybod
On Tuesday, 27 February 2018 15:23:16 CET Luca Beltrame wrote:
> Il giorno Tue, 27 Feb 2018 14:58:22 +0100
> Boudewijn Rempt ha
>
> scritto:
> > * A bug nobody has looked at yet
>
> How would NEW not fit the bill? (As opposed to UNCONFIRMED)
>
> > * A bug someone other than the reporter has loo
Il giorno Tue, 27 Feb 2018 14:58:22 +0100
Boudewijn Rempt ha
scritto:
> * A bug nobody has looked at yet
How would NEW not fit the bill? (As opposed to UNCONFIRMED)
> * A bug someone other than the reporter has looked at, but which was
> not reproducible
Do you mean a single status that covers
On 27.02.2018 15:45, Paul Brown wrote:
On Tuesday, 27 February 2018 13:43:17 CET Boudewijn Rempt wrote:
On Tuesday, 27 February 2018 13:30:12 CET Paul Brown wrote:
Is it true that users get confused by the bugtracking system? If so, this
is an issue, right?
Well, users can get confused by _ev
On Tuesday, 27 February 2018 14:45:51 CET Paul Brown wrote:
> On Tuesday, 27 February 2018 13:43:17 CET Boudewijn Rempt wrote:
> > On Tuesday, 27 February 2018 13:30:12 CET Paul Brown wrote:
> > > Is it true that users get confused by the bugtracking system? If so,
> > > this
> > > is an issue, rig
On Tuesday, 27 February 2018 13:43:17 CET Boudewijn Rempt wrote:
> On Tuesday, 27 February 2018 13:30:12 CET Paul Brown wrote:
> > Is it true that users get confused by the bugtracking system? If so, this
> > is an issue, right?
>
> Well, users can get confused by _everything_.
If a service is co
On 27.02.2018 14:43, Boudewijn Rempt wrote:
On Tuesday, 27 February 2018 13:30:12 CET Paul Brown wrote:
Is it true that users get confused by the bugtracking system? If so, this is
an issue, right?
Well, users can get confused by _everything_. Though I probably have more
absolutely non-technic
As a newcomer, I didn't realize I was allowed to change UNCO to CONF and
did so only when absolutely positive the issue existed. But I've already
seen issues like a user who continually reports bugs (often enough that I
recognize the name from among thousands).
When I triage something and find it
Il giorno Tue, 27 Feb 2018 13:43:17 +0100
Boudewijn Rempt ha
scritto:
> KDE projects. I haven't seen many signs of users being confused by
> UNCONFIRMED vs CONFIRMED, though.
At least in certain forums (not necessarily the KDE forums, this
includes media like reddit), "UNCONFIRMED" is often seen
On Tuesday, 27 February 2018 13:28:50 CET Boudewijn Rempt wrote:
> I thought I was clear enough, users should report bugs in bugs.kde.org. They
> should not report bugs anywhere else. Not on phabricator, the forum,
> reddit, twitter, tumblr, devianart, blenderartists, google+, facebook or
> through
On Tuesday, 27 February 2018 13:30:12 CET Paul Brown wrote:
> Is it true that users get confused by the bugtracking system? If so, this is
> an issue, right?
Well, users can get confused by _everything_. Though I probably have more
absolutely non-technical users reporting bugs than most other KD
On Tuesday, 27 February 2018 13:16:03 CET Aleix Pol wrote:
> On Tue, Feb 27, 2018 at 12:22 PM, Paul Brown wrote:
> > On Tuesday, 27 February 2018 11:51:42 CET Boudewijn Rempt wrote:
> >> On Tuesday, 27 February 2018 11:47:22 CET Paul Brown wrote:
> >> > On Tuesday, 27 February 2018 11:41:04 CET Bo
On Tuesday, 27 February 2018 12:22:51 CET you wrote:
> On Tuesday, 27 February 2018 11:51:42 CET Boudewijn Rempt wrote:
> > On Tuesday, 27 February 2018 11:47:22 CET Paul Brown wrote:
> > > So... where are users supposed to report bugs?
> >
> > Users report bugs in bugs.kde.org.
>
> I'll ask the
On Tue, Feb 27, 2018 at 12:22 PM, Paul Brown wrote:
> On Tuesday, 27 February 2018 11:51:42 CET Boudewijn Rempt wrote:
>> On Tuesday, 27 February 2018 11:47:22 CET Paul Brown wrote:
>> > On Tuesday, 27 February 2018 11:41:04 CET Boudewijn Rempt wrote:
>> > > Given that bugzilla is a tool for devel
On Tuesday, 27 February 2018 11:51:42 CET Boudewijn Rempt wrote:
> On Tuesday, 27 February 2018 11:47:22 CET Paul Brown wrote:
> > On Tuesday, 27 February 2018 11:41:04 CET Boudewijn Rempt wrote:
> > > Given that bugzilla is a tool for developers, I don't care that users
> > > might
> > > get confu
On Tuesday, 27 February 2018 11:47:22 CET Paul Brown wrote:
> On Tuesday, 27 February 2018 11:41:04 CET Boudewijn Rempt wrote:
> > Given that bugzilla is a tool for developers, I don't care that users
> > might
> > get confused.
> >
> > > We don't have this problem with phabricator tasks because t
Il giorno Tue, 27 Feb 2018 11:32:10 +0100
Elvis Angelaccio ha
scritto:
> The UNCONFIRMED/CONFIRMED thing has little meaning, is confusing for
> users and for new triagers and we know that many developers never set
+1 On setting it to NEW. That's what we have in openSUSE and has a much
better mea
On Tuesday, 27 February 2018 11:41:04 CET Boudewijn Rempt wrote:
> Given that bugzilla is a tool for developers, I don't care that users might
> get confused.
>
> > We don't have this problem with phabricator tasks because they can be
> > either Open or closed (for whatever reason).
>
> I don't l
On Tuesday, 27 February 2018 11:32:10 CET Elvis Angelaccio wrote:
> Hi,
> recently we introduced a policy change in bugzilla and now every user has
> the power to change the status of any ticket.
>
> This is good (and consistent with phabricator) but there is a big downside:
> many people will ope
Hi,
recently we introduced a policy change in bugzilla and now every user has
the power to change the status of any ticket.
This is good (and consistent with phabricator) but there is a big downside:
many people will open a new ticket and then mark it as CONFIRMED. This is
annoying because no
42 matches
Mail list logo