Re: Bug Tracking

Tony Payne wrote:
> 
> > > *) How long until we could have a perl6 database up and functioning?  I
Not so long :-)

> A product field is probably the cleanest option, but a new database would be
> acceptable to me.
A product field, it is, then - makes it easier for admins to be on several
different tracks, and not have to hop about between databases too.

> > > *) Will it forward email based on the category of the bug (core,
> standard
<snip>
> > Now we have this neat namespace, would that not be able to cover it too,
> > [email protected]
> > etc?  Note that this particular line is not currently implemented
> That is pretty much the functionality I was hoping for.  Is it easy to add
> new rules?
Yup.

> > Hmmmm, sounds like we need a test table:
> > n tests <-> n tickets
> Good point.  It certainly could eventually be a many-to-many relationship.
> However, I think when a bug is reported, one test field would probably be
OK.

> One nice thing with this suggestion is that we could actually use the bug
> database as the test repository.  And maybe could extend some of the bug
> concepts to tests as well.  For example, the ability to mark tests as
> duplicates would help keep the testbed down to a reasonable subset.
Do tests go against bugs, or do they go against patches, or do they go against
versions, or what etc?

Ciao
Richard Foley
---
[email protected] | [email protected] | [email protected]
'Ciao' - shorter than 'Aufwiedersehen'