From:  Flore Allemandou <flore@mozfr.org>
Date:  26 Mar 2016 01:44:49 Hong Kong Time
Newsgroup:  news.mozilla.org/mozilla.bugmasters
Subject:  

Re: Dealing with old bugs

NNTP-Posting-Host:  63.245.214.181

Thanks Wes for your answer,

In the meantime I found guidelines for bugzilla, that could be useful for
all the newbies (including me) trying to help on bugzilla:
https://developer.mozilla.org/en-US/docs/Mozilla/Bugzilla/What_to_do_and_what_not_to_do_in_Bugzilla

It basically answered my current questions. I also found another helpful
page:
https://developer.mozilla.org/en-US/docs/Mozilla/QA/Confirming_unconfirmed_bugs

Could be a good reference for future contributors too.

Have a nice day

2016-03-25 18:05 GMT+01:00 Wes KWierso :

>
>
> WORKSFORME or INVALID or INCOMPLETE would all work. FIXED would really
> only apply if you could find some code change that actually fixed the
> issue.
>
>
>
> Honestly, though, I’d argue that micromanaging the bug graveyard isn’t
> hugely important. The important part is closing out the old, not relevant
> bugs so that the still open bugs paint a better picture of the current
> state of that product.
>
>
>
> *From: *Flore Allemandou 
> *Sent: *Friday, March 25, 2016 4:01 AM
> *To: *bugmasters@lists.mozilla.org
> *Subject: *Re: Dealing with old bugs
>
>
> Hi Wes,
>
> I'm asking myself the same questions as Scott.
> When encountering a bug that does not happen anymore in new versions (I saw
> one for version 4.0 which works now), what is the correct resolution ?
> I would be inclined to update : RESOLVED -> FIXED
> Because, it was a real bug when it was filed so WORKSFORME does not really
> seem relevant.
>
> I'm "training" on old bugs that look easy. and I was wondering on best
> practices: closing as many old bugs as we can or let them die buried under
> piles of new bugs ? I don't want to be a pain and flooding people with
> bugmails on very old forgotten bugs.
>
> Thanks for helping bugpadawans!
>
> 2016-03-25 8:31 GMT+01:00 Wes KWierso :
>
> > In this particular case, I’d ask in the bug if the situation is still
> > reproducible with modern versions of Firefox. If you don’t get an answer
> in
> > a few days, close it with a comment asking the reporter to reopen or
> file a
> > new bug if they’re still having the problem. (You could likely get away
> > with just closing the bug and leaving the comment to reopen/refile, but
> > it’s nice to give a chance for them to speak up first.)
> > Wes
> > From: Scott Macpherson >
> > Sent: Thursday, March 24, 2016 11:39 PM
> > To: bugmasters@lists.mozilla.org
> > Subject: Dealing with old bugs
> >
> > Hi all. What's the best way for a Bugzilla newbie to help deal with old
> > bugs which are suspected to be invalid or dead? For example, 984152
> > hasn't been touched for two years, and doesn't have a huge amount of
> > details to help with confirmation. It reads like a feature request
> > rather than a bug as well.
> >
> > https://bugzilla.mozilla.org/show_bug.cgi?id=984152
> >
> > Cheers,
> > Scott.
> > _______________________________________________
> > bugmasters mailing list
> > bugmasters@lists.mozilla.org
> > https://lists.mozilla.org/listinfo/bugmasters
> > _______________________________________________
> > bugmasters mailing list
> > bugmasters@lists.mozilla.org
> > https://lists.mozilla.org/listinfo/bugmasters
> >
>
>
>
> --
> Flore
> _______________________________________________
> bugmasters mailing list
> bugmasters@lists.mozilla.org
> https://lists.mozilla.org/listinfo/bugmasters
>



-- 
Flore