docs/clarification on confirming

[C de-Avillez]

On Wed, 2010-06-23 at 21:47 -0400, David Tombs wrote:
> Hi Serge,
> 
> I'm no expert, but I'd actually say dealing with patches upstream
> probably means the bug is no longer being /triaged/ but being fixed.
> Perhaps "In Progress" would be better for this situation? I'm not sure
> about the official answer.

and the original Q from Serge:

> I'm looking https://wiki.ubuntu.com/Bugs/HowToTriage while also
> > looking at some bugs.  The 'Confirming' section suggests that if
> > a submitter submits a patch, and we ask them to push the patch
> > upstream to a mailing list (per upstream policy), then these
> > should be marked confirmed.  But it looks like in practice it is
> > assumed that this represents a request for action on part of
submitter,
> > and bugs are then placed in 'Incomplete' state.
> 

Hi David, Serge,

No, not in progress. In progress is used when  *we* are actively working
in a fix -- and, if upstream is the party responsible, *we* are not
working actively on the bug.

In this case, the bug should have been upgraded to Triaged, and an
upstream task opened for it, but with *no* bug number (yet) at this
point in time. When the OP submits the patch upstream (which will most
probably be via a bug upstream), then we can add the bug number on the
bug's upstream task.

Yes, this is a request for action to the submitter. This is, most
probably, because whoever was dealing with this bug did not have the
free time necessary to do the upstreaming themselves. Technically,
though, the bug is not incomplete, and should not be marked as such.

There is no real fast & hard rule. It is a mix of what we want to happen
(the wiki's pages) and the Real Work (TM) required adjustments.

-- 
C de-Avillez
IRC: hggdh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20100623/c79cd386/attachment.sig>