Re: [Mageia-dev] Proposal for bug statuses and workflow

2011-10-20 Thread andre999

Samuel Verschelde a écrit :

Here is a workflow proposal for bug reports in bugzilla.
   

[...]

Best regards

Samuel Verschelde
   


I think it is really well thought out.
Especially renaming certain statuses, to better coincide with their usage.
The resolutions as well.

Only one question :
The NEW + triaged keyword status seems ok, but I can see Marja's point 
that it might be better to have an explicit TRIAGED status.

What happens if the bug is not ACCEPTED, or there is no maintainer ?
The bug is just left in this state ?

(Looks like you're making good use of the Libreoffice Draw flowcharting.)

In sum, WORKS_FOR_ME :)

--
André



Re: [Mageia-dev] Proposal for bug statuses and workflow

2011-10-20 Thread Romain d'Alverny
On Wed, Oct 19, 2011 at 23:30, Samuel Verschelde sto...@laposte.net wrote:
 CLOSED replaces RESOLVED, because I think it's nicer for the bug reporter if
 we close bugs rather than consider them resolved when the reason for
 closing is WONT-FIX, DUPLICATE, OLD, etc., statuses that obviously don't match
 the meaning of RESOLVED.

RESOLVED does match.

Beware, this is a known false friend in English/French (although it
is used in a equivalent meaning as in Je suis résolu à or J'ai pris
la ferme résolution de). To resolve is to decide firmly, not to solve
(well, as well, but in a later meaning).

If the RESOLVED status in Bugzilla had been understood as SOLVED,
then RESOLVED - FIXED would be a pleonasm.

Romain


Re: [Mageia-dev] Proposal for bug statuses and workflow

2011-10-20 Thread Guillaume Rousse

Le 20/10/2011 10:26, Romain d'Alverny a écrit :

If the RESOLVED status in Bugzilla had been understood as SOLVED,
then RESOLVED - FIXED would be a pleonasm.
You can solve a problem differently than fixing it, for instance by 
claiming it is not a problem, or that it is too old to really care.

--
BOFH excuse #138:

BNC (brain not connected)


Re: [Mageia-dev] Proposal for bug statuses and workflow

2011-10-20 Thread Romain d'Alverny
On Thu, Oct 20, 2011 at 10:43, Guillaume Rousse guillomovi...@gmail.com wrote:
 Le 20/10/2011 10:26, Romain d'Alverny a écrit :

 If the RESOLVED status in Bugzilla had been understood as SOLVED,
 then RESOLVED - FIXED would be a pleonasm.

 You can solve a problem differently than fixing it, for instance by claiming
 it is not a problem, or that it is too old to really care.

That's precisely the resolution to the problem: fixed (and the
solution is provided along here) or discarded or reported elsewhere.
https://bugs.mageia.org/page.cgi?id=fields.html#status is more visual
about this.

Romain


Re: [Mageia-dev] Proposal for bug statuses and workflow

2011-10-20 Thread José Jorge
Le jeudi 20 octobre 2011 06:35:32, Marja van Waes a écrit :
 BTW, replacing status NEW + keyword Triaged by status TRIAGED, and
 leaving all the rest the same, would solve another problem and save time ;)

+1 The less keywords we have, the better is : they are error prone.
NEEDINFO can't be a status as it may happen everywhere in the workflow, but 
TRIAGED is only once.


Re: [Mageia-dev] Proposal for bug statuses and workflow

2011-10-20 Thread Manuel Hiebel
Le mercredi 19 octobre 2011 à 23:30 +0200, Samuel Verschelde a écrit :
 Here are the proposed Resolutions:
Another thing, what about the upstream reported bugs ?
In Mandriva they have a status REPORTEDUPSTREAM (if the triage_guide is
true)
Can we do the same ? 
http://mageia.org/wiki/doku.php?id=triage_guide#is_it_an_issue_that_should_be_covered_by_the_mageia_bug_process





Re: [Mageia-dev] Proposal for bug statuses and workflow

2011-10-20 Thread andre999

Romain d'Alverny a écrit :

On Wed, Oct 19, 2011 at 23:30, Samuel Verscheldesto...@laposte.net  wrote:
   

CLOSED replaces RESOLVED, because I think it's nicer for the bug reporter if
we close bugs rather than consider them resolved when the reason for
closing is WONT-FIX, DUPLICATE, OLD, etc., statuses that obviously don't match
the meaning of RESOLVED.
 

RESOLVED does match.

Beware, this is a known false friend in English/French (although it
is used in a equivalent meaning as in Je suis résolu à or J'ai pris
la ferme résolution de). To resolve is to decide firmly, not to solve
(well, as well, but in a later meaning).
   


Sorry, but I think they have the same meanings in English and French.
Which isn't surprising, considering that it comes from French.
[...]

Romain
   


In English, RESOLVED can refer to decision, solving, or something in 
between.


In the context of a bug report, what are we doing ?
Maybe we discovered what the problem was.  Maybe we fixed it, maybe not.
But whatever the reason, the action is closing the report.
Let's avoid obtuse language,
 and simply say CLOSED.
It has the advantage of being able to give a clear reason of fixed, 
without any redundancy.


aside
This reminds me of proceedings at political conventions :
Whereas ...
and ...
be it resolved that ...
(Usually something that is never done.)
/aside

--
André



Re: [Mageia-dev] Proposal for bug statuses and workflow

2011-10-20 Thread Florian Hubold

Am 19.10.2011 23:30, schrieb Samuel Verschelde:

Here is a workflow proposal for bug reports in bugzilla.

See the flowchart (link below) and the explanations below. Not all statuses
will be used in every bug report, but the flowchart more or less gives the
standard flow for bugs reported against a stable release of Mageia.

http://stormi.lautre.net/fichiers/mageia/triage.png

NEW: as currently, bugs are set to this status when created

NEW (+ NEEDINFO keyword): more input needed

Why not set NEEDINFO keyword by default when a bug is reported and
a triager or the maintainer removes it then if sufficient information to work
on this bug is already present?

I'd say this being a keyword and not mandatory it will be forgotten often IMHO.

NEW (+ Triaged keyword):

ACCEPTED

IN_PROGRESS
really fine-grained but useless IMHO. If it has been triaged, there should be 
someone

who works on that bug, and what reason would there be to not accept a bug?

Just my humble opinion. If those help to ease triage, why not.


Re: [Mageia-dev] Proposal for bug statuses and workflow

2011-10-20 Thread David W. Hodgins

On Wed, 19 Oct 2011 17:30:05 -0400, Samuel Verschelde sto...@laposte.net 
wrote:


VALIDATED is set by QA team once testing ends. It means that the update can be
pushed (replaces the validated_update keyword)


Will changing the status automatically update the assigned, for Testing
and Validated?  If changing the status to Validated changes the assigned
from qa-bugs to sysadmin-bugs, qa-bugs should be added to the cc list.

Regards, Dave Hodgins


Re: [Mageia-dev] Proposal for bug statuses and workflow

2011-10-19 Thread Maarten Vanraes
Op woensdag 19 oktober 2011 23:30:05 schreef Samuel Verschelde:
 Here is a workflow proposal for bug reports in bugzilla.
[...]

This is ok for me, i like the resolutions as well.


Re: [Mageia-dev] Proposal for bug statuses and workflow

2011-10-19 Thread Marja van Waes

Op 19-10-11 23:30, Samuel Verschelde schreef:

Here is a workflow proposal for bug reports in bugzilla.


I think it looks great, it solves several of the Bug Squad's problems :)


Re: [Mageia-dev] Proposal for bug statuses and workflow

2011-10-19 Thread Marja van Waes

Op 19-10-11 23:45, Marja van Waes schreef:

Op 19-10-11 23:30, Samuel Verschelde schreef:

Here is a workflow proposal for bug reports in bugzilla.


I think it looks great, it solves several of the Bug Squad's problems :)



BTW, replacing status NEW + keyword Triaged by status TRIAGED, and 
leaving all the rest the same, would solve another problem and save time ;)