Okay, I've responded to some of the additions.
> Use of the candidate DTS with advanced file system
> capabilities should be defined. (For example: Can ZFS clones be used
> to | back up the defect corpus, or is consistency enforced
> above the | file system layer?)
Currently it's enforced by Bugzilla itself and also by MySQL.
Bugzilla 3.2 will also enforce referential integrity at the database
level.
> | - associate defect with a list of parties desiring defect
> update | notifications
Yes, any DTS that doesn't do that would be a sad DTS. :-)
> | E11. Non-hierarchical defect classification
Yes, Bugzilla supports this with keywords and flags. (Flags are
a way of having a keyword and then that keyword having a state of
"?" [for "somebody please say yes or no"], "+" [for "yes"] or "-" [for
"no"].)
> | E12. Concurrent change detection, basic
Yes, Bugzilla warns you when you try to change a bug that
somebody else changed while you were looking at it.
> | E13. Unicode data representation
Yes, Bugzilla has excellent Unicode support.
> | E15. Versioned or audited defect history
Bugzilla lists the history of all changes. It doesn't currently
have a rollback, but rollback is almost never needed, and so doing it
manually (by looking at the history) works fine for every installation
that I know of.
> | C19. Concurrent change detection, enhanced
Yes, Bugzilla allows you to say "commit my changes anyway" and
thus apply them to the latest version of the bug.
-Max
--
http://www.everythingsolved.com/
Competent, Friendly Bugzilla Services. And Everything Else, too.
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
