Vince asks:
> Everybody keeps saying bugzilla. What EXACTLY will bugzilla do for us
> that would make me want to learn it and install it? BTW, the current
> wheel was invented a year ago 'cuze nothing really fit what we needed.
The reasons I would choose Bugzilla:
1. It's *not* written by us so (in theory) we don't have to waste time
developing yet another bug tracking solution.
2. It sends email to people involved with a bug whenever the detail
associated with that bug is modified. This includes the reporter, who
often will feedback that it now works, at which time the fixer or the
reporter can mark the bug as fixed.
3. It complains when a NEW bug hasn't been looked at for /n/ days --
this means that any not-a-bug's will be closed, while any that are
really bugs will be accepted.
4. Good query facilities, if a little complex to use.
5. I think Bugzilla's concepts of products, components and versions fit
the way we work.
I envisage that 'Postgres', 'Interfaces', 'Languages' might be products
that we would have.
Within 'Postgres' we would have the various subsystems that make up the
core.
Within 'Interfaces' we would have 'JDBC', 'ODBC' etc.
Within 'Languages' we would have 'PL/pgSQL' etc.
Arguments accepted.
There are other tools the Mozilla project uses that we could also use:
Tinderbox -- continuous automated builds, including subsequent regression
tests
(useful for seeing who broke CVS).
Bonsai -- CVS integration for Bugzilla
Cheers,
Colin
