Document Foundation Mail Archive › LibreOffice › QA

[Libreoffice-qa] RESOLVED status question

Classic

List

Threaded

5 messages Options

jmadero

[Libreoffice-qa] RESOLVED status question

At what point do we put resolved as a status? Is it when it's committed to master branch? If not then is the developer/qa team expected to continue to check a patchs status after it's already committed to master in order to find out if it's committed elsewhere? Thanks in advance, I'm not positive I've been doing it right :-/ A few I marked as RESOLVED because I know they are fixed in master and will soon be seen by other users as resolved as well.

Thanks again,

Joel

_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: [hidden email]
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

Petr Mladek

Re: RESOLVED status question

Joel Madero píše v Čt 02. 08. 2012 v 14:42 -0700:
> At what point do we put resolved as a status? Is it when it's
> committed to master branch? If not then is the developer/qa team
> expected to continue to check a patchs status after it's already
> committed to master in order to find out if it's committed elsewhere?
> Thanks in advance, I'm not positive I've been doing it right :-/ A few
> I marked as RESOLVED because I know they are fixed in master and will
> soon be seen by other users as resolved as well.

I would mark it as RESOLVED when the fix is pushed in all branches where
we want it. IMHO, it means that the work is done from the developer
side.

We always want it in master. Sometimes, we want to backport it into
older products which need some developer input as well.

Best Regards,
Petr

_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: [hidden email]
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

jmadero

Re: RESOLVED status question

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.

Best Regards,

Joel

On Tue, Aug 7, 2012 at 3:29 AM, Petr Mladek <[hidden email]> wrote:

Joel Madero píše v Čt 02. 08. 2012 v 14:42 -0700:

> At what point do we put resolved as a status? Is it when it's
> committed to master branch? If not then is the developer/qa team
> expected to continue to check a patchs status after it's already
> committed to master in order to find out if it's committed elsewhere?
> Thanks in advance, I'm not positive I've been doing it right :-/ A few
> I marked as RESOLVED because I know they are fixed in master and will
> soon be seen by other users as resolved as well.

I would mark it as RESOLVED when the fix is pushed in all branches where
we want it. IMHO, it means that the work is done from the developer
side.

We always want it in master. Sometimes, we want to backport it into
older products which need some developer input as well.

Best Regards,
Petr

Petr Mladek

Re: RESOLVED status question

Hi,

If you see the automatic comment about that a fix was committed and you
are not longer able to reproduce the problem, I prefer to close it as
RESOLVED FIXED. In this case, it is clear that a developer committed
something for this particular bug. Someone fixed it by intention.

Otherwise, if it started to work without any commit message, I would
close it as WORKSFORME.

I hope that it makes sense :-)

Keep the great work on cleaning bugzilla.

Best Regards,
Petr

Joel Madero píše v Po 13. 08. 2012 v 10:13 -0700:

> 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.
>
>
>
>
> Best Regards,
> Joel
>
> On Tue, Aug 7, 2012 at 3:29 AM, Petr Mladek <[hidden email]> wrote:
> Joel Madero píše v Čt 02. 08. 2012 v 14:42 -0700:
> > At what point do we put resolved as a status? Is it when
> it's
> > committed to master branch? If not then is the developer/qa
> team
> > expected to continue to check a patchs status after it's
> already
> > committed to master in order to find out if it's committed
> elsewhere?
> > Thanks in advance, I'm not positive I've been doing it
> right :-/ A few
> > I marked as RESOLVED because I know they are fixed in master
> and will
> > soon be seen by other users as resolved as well.
>
>
> I would mark it as RESOLVED when the fix is pushed in all
> branches where
> we want it. IMHO, it means that the work is done from the
> developer
> side.
>
> We always want it in master. Sometimes, we want to backport it
> into
> older products which need some developer input as well.
>
>
> Best Regards,
> Petr
>
>
>
>
> _______________________________________________
> List Name: Libreoffice-qa mailing list
> Mail address: [hidden email]
> Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
> Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
> Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
> List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

Bjoern Michaelsen

Re: RESOLVED status question

Hi,

On Wed, Aug 15, 2012 at 12:01:31PM +0200, Petr Mladek wrote:
> If you see the automatic comment about that a fix was committed and you
> are not longer able to reproduce the problem, I prefer to close it as
> RESOLVED FIXED. In this case, it is clear that a developer committed
> something for this particular bug. Someone fixed it by intention.
>
> Otherwise, if it started to work without any commit message, I would
> close it as WORKSFORME.

So IMHO, in an ideal world we would have:

no statement from dev he thinks it is fixed, but QA cant reproduce it anymore => RESOLVED/WORKSFORME (and maybe ping the dev about it)
statement from the dev he thinks it is fixed, but not checked by QA => RESOLVED/FIXED
statement from the dev he thinks it is fixed, but QA finds otherwise => REOPENED
statement from the dev he thinks it is fixed, checked by QA => VERIFIED/FIXED
statement from the dev he thinks it is fixed, checked by QA, released in a non-rc/non-beta/non-daily => CLOSED/FIXED

Best,

Bjoern
_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: [hidden email]
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/