The Next Step Was: Re: Bugzilla - an experiment in trackability

[Brad Roberts]

On Mon, 6 Mar 2006, Kyle Furlong wrote:

> Brad Roberts wrote:
> > Ok.. it's probably a little rough still, but I think it's usable now.  I've
> > got bugzilla setup here:
> > 
> >     http://d.puremagic.com/bugzilla/
> > 
> > Any new bugs or changes to existing bugs will be sent through to
> > digitalmars.D.bugs.  Any messages posted in the newsgroup with the subject
> > matching /bugs.*\d+/i will be auto appended to the referenced bug if the
> > 'from' email address matches a registered user.  The entire body of the
> > message will be recorded, so please trim the body down to the really
> > relevant information.  There's no need for the body to contain the entire
> > contents of all past conversations since they will already be in the db.
> > 
> > I have NOT gone back and opened bugs for already reported bugs, except the
> > one I used for testing.  Please feel free to do so for bugs you know to be
> > still open.
> > 
> > The products and components available for filing bugs are still somewhat
> > skeletal.  I'm sure there will be some rearrangements as we start to
> > accumulate data.
> > 
> > I'm certainly open to suggestions on all facets of the system.  My goal is
> > to provide a trackable system that allows us all to better understand the
> > state of the d language and it's supporting pieces.
> > 
> > If you'd prefer to comment privately, that's welcome as well.
> > 
> > Later,
> > Brad
> 
> The obvious next step is for Walter to allow trusted community members the
> ability to fix bugs under a certain priority level. Ready? Discuss!

Um.. I'm sure he's already willing to accept fixes from anyone for any 
bug.  There's no guarantee that he'll take the change 'as is', but I'm 
_sure_ he's happy to have others diagnose and provide fixes for bugs.

Part of what's needed is a way to understand what bugs are being worked 
on.  Bugzilla provides that, but it requires that people actually use it 
well.  New bugs come in as status 'NEW'.  There's a radio button below the 
comment block for the bug to be changed to 'assigned' aka 'accepted, I'm 
working on it now'.

So, don't wait for feedback from walter on this.. just dive in and help.  
Granted, providing fixes for backend dmd bugs can't be done by anyone 
other than him, but anything in the front end and semantic level of the 
language and compiler can be fixed through gdc.  They share a front end.

Once you have fixes, attach diffs to the bug entry.

Later,
Brad