duplicate bugs procedure? -was- Re: [wp-hackers] Finding bugs to
fix on Trac
Dr. Mike Wendell
theapparatus at gmail.com
Thu Feb 22 20:02:33 GMT 2007
On 2/22/07, Lloyd Budd <lloydomattic at gmail.com> wrote:
> On 2/22/07, Dr. Mike Wendell <theapparatus at gmail.com> wrote:
> > On 2/22/07, Ryan Boren <ryan at boren.nu> wrote:
> > > On 2/21/07, Jennifer Hodgdon <yahgrp at poplarware.com> wrote:
> > > We have a few keywords we use: commit, has-patch, dev-feedback,
> > > 2nd-opinion, needs-testing, reporter-feedback. The various reports
> > > created from these are here:
> > While I'm sitting here looking at it, what's the procedure for dupe
> > tickets? I'm looking at 3063 and 3917 for reference, the new Blogger
> > importer.
> What do you mean by procedure?
> You comment on the duplicate and you close the one with the least relevant info.
Didn't know if it was "cool" for end-users to close tickets. We try
not to do that over on the WPMu trac, well at least I try to leave it
for Donncha to make a final decision.
I was wondering if there was a way to flag a ticket as a dupe so that
someone in charge could come along and close it. Like a modlook tag
that we use in the forums.
Kim Possible: Remixed: http://kimpossibleremixed.com
Get your own free hosted WordPress Blog today: http://daria.be
More information about the wp-hackers