Re: patchwork.sourceware.org is live!

[Siddhesh Poyarekar <siddhesh.poyarekar@gmail.com>]

On 27 May 2014 11:52, Thomas Schwinge <thomas@codesourcery.com> wrote:
>> close patches you know you have already pushed into master.
>
> Does that mean changing the state to »Accepted« (or »Committed«, once
> that has been added), or ticking the »Archived« box, or both?  What's the
> meaning of the »Archived« box?

Only change to Accepted for now, since nobody has commented on my
suggestion to add a new Committed status.  I have no idea what the
Archived checkbox does :)

> So, does patchwork's »Delegate to« Patch Property equal Bugzilla's
> »Assigned To« field?  And, it is not totally clear to my why the Patch
> Review Workflow suggests to »not change the status of the patch« if
> »changing the Delegate to value to their patchwork username«?

That suggestion is no longer necessary.  I have added the 'Under
Review' and 'Change Requested' statuses to the default view, so
changing state should not make those patches disappear from the queue
unless the state is Accepted, Superseded, RFC or Rejected.

> "In a perfect world", after a patch review, during which »Delegate to«
> has been set to the reviewer(s), should it then be changed to the person
> who is responsible for committing the patch (which may be the submitter,
> or the reviewer, or someone else), together with changing the state to
> »Accepted«?

Yes, that would be good idea.

Siddhesh
-- 
http://siddhesh.in