agree more.
Here is a perfect example of an ASSIGNED bug which could (probably) already
been fixed
https://bugs.freedesktop.org/show_bug.cgi?id=38451
--
View this message in context:
http://nabble.documentfoundation.org/Re-Bug-Status-NEW-but-Assigned-to-Someone-Please-Change-tp4029440p4029569
Hi All,
I just noticed on FDO we have over 400 bugs that are in NEW status but are
not assigned to default (ie. someone is assigned). If you have any bugs
that are assigned to you but that are in NEW, can you change this to
ASSIGNED or release the bug so someone else might take a look at it.
On 01/15/2013 01:32 PM, Joel Madero wrote:
Hi All,
I just noticed on FDO we have over 400 bugs that are in NEW status but
are not assigned to default (ie. someone is assigned). If you have any
bugs that are assigned to you but that are in NEW, can you change this
to ASSIGNED or release the bug
On 01/15/2013 01:39 PM, Kohei Yoshida wrote:
I don't see any need to reset those to the default account. IMO that
would only create unnecessary noise for no gain. And I don't think it's
appropriate to ask the assignee to endure that double pain (of going
through those bugs that someone else
On Tue, Jan 15, 2013 at 10:53 AM, Kohei Yoshida kohei.yosh...@gmail.comwrote:
'm only work on one at the moment, and it's easier for me to just change
the one I'm working on.
I didn't realize it was a previous policy. I'll bring up during QA call to
see if we want to keep this. I think
Kohei Yoshida schrieb:
Hi all,
I think I understand Joel's intention. I also have problems to find out
whether a bug already is under observation of a developer (because he is
in CC), that was more easy in the early time with very few developers.
And I believe developers should become
So I agree with Kohei, we should not modify this if we do not have very
good reasons with really promising prospects for benefit. Of course, if
someone has ideas here, we should discuss that (may be better on qa list?).
+1, let's take this off developer list and come up with a good solution
Kohei Yoshida schrieb:
Hi all,
I think I understand Joel's intention. I also have problems to find out
whether a bug already is under observation of a developer (because he is
in CC), that was more easy in the early time with very few developers.
And I believe developers should become
So I agree with Kohei, we should not modify this if we do not have very
good reasons with really promising prospects for benefit. Of course, if
someone has ideas here, we should discuss that (may be better on qa list?).
+1, let's take this off developer list and come up with a good solution
that someone
picks it forward...
Sorry for the reality check ;)
--
View this message in context:
http://nabble.documentfoundation.org/Re-Bug-Status-NEW-but-Assigned-to-Someone-Please-Change-tp4029440p4029505.html
Sent from the QA mailing list archive at Nabble.com
Hi,
On Tue, Jan 15, 2013 at 02:46:11PM -0800, bfo wrote:
I read this data as NEW backlog - nobody is interested in those reports.
IMHO QA hard work to transform a bug into NEW state is pretty much wasted,
as I consider NEW stated bugs as ready to start fixing...
There are only so many
11 matches
Mail list logo
