Rockbox mail archive
Subject: Re: bug report closing (was Re: Release policy and coordination)
Re: bug report closing (was Re: Release policy and coordination)
by any1 able to close u mean just the mods right?
also i know its a pain... (unless FS can automate this), but it should
not be closed straight away with the message "it should be fixed.."
unless its 100% garenteed fixed on all targets... mabye wait a week
for confirmation from the reporter? (like i said i know it woudl be a
pain.. but not all fixes work perfectly..)
also, maybe close and remove all bug reports and patches that are
older than a few months? if they are still bugs then they can be
reported again, and patches are most likely out of date anyway...
On 31/05/06, Paul Louden <firstname.lastname@example.org> wrote:
> I agree, with the ability of anyone to close bug reports, you should be able
> to close them with a message like "This should be fixed in CVS now. Open a
> new one if the bug still exists, with updated instructions on how to
> reproduce them with a new build."
> On 5/31/06, Daniel Stenberg <email@example.com> wrote:
> > On Tue, 30 May 2006, Zakk Roberts wrote:
> > > iPod bug reports, and the policy is not clear to me on how aggressive we
> > > should be about closing them because they aren't supported models. I
> > > several of the 'should-be-fixed' ones are also still open even after
> > > are committed with comments from the devs asking "is this fixed with
> > > CVS?" and getting no response;
> > My position on this: *all* bugs that have an outstanding question that
> > to be answered for the bug case to "move forward" SHOULD be closed if
> > replies to the open question within two weeks.
> > If the submitter happens to be legitimately away for that period, he/she
> > always re-open the task later or submit a new bug report.
> > --
> > Daniel Stenberg -- http://www.rockbox.org/ -- http://daniel.haxx.se/
Received on Wed May 31 07:35:48 2006
Page was last modified "Jan 10 2012" The Rockbox Crew