Thanks Peter. Given the information you and Rainer provided I think the best thing for QA triagers to do is to mark as WORKSFORME in most cases unless they know specifically that the bug was fixed and then maybe CC the person who patched the bug so they see the bug is closed. If this isn't the best method please let me know what is. <div>
<br></div><div><br></div><div>Best Regards,</div><div>Joel<br><br><div class="gmail_quote">On Tue, Aug 7, 2012 at 3:29 AM, Petr Mladek <span dir="ltr"><<a href="mailto:pmladek@suse.cz" target="_blank">pmladek@suse.cz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Joel Madero píše v Čt 02. 08. 2012 v 14:42 -0700:<br>
<div><div class="h5">> At what point do we put resolved as a status? Is it when it's<br>
> committed to master branch? If not then is the developer/qa team<br>
> expected to continue to check a patchs status after it's already<br>
> committed to master in order to find out if it's committed elsewhere?<br>
> Thanks in advance, I'm not positive I've been doing it right :-/ A few<br>
> I marked as RESOLVED because I know they are fixed in master and will<br>
> soon be seen by other users as resolved as well.<br>
<br>
</div></div>I would mark it as RESOLVED when the fix is pushed in all branches where<br>
we want it. IMHO, it means that the work is done from the developer<br>
side.<br>
<br>
We always want it in master. Sometimes, we want to backport it into<br>
older products which need some developer input as well.<br>
<br>
<br>
Best Regards,<br>
Petr<br>
<br>
<br>
</blockquote></div><br></div>