Confirmed users
729
edits
Bugzilla Fixup: Difference between revisions
Jump to navigation
Jump to search
+1 to removing bug fields
(too many fields) |
(+1 to removing bug fields) |
||
| Line 49: | Line 49: | ||
* dolske: Integrate with [[Build:TryServer]], to allow submitting a patch directly from Bugzilla | * dolske: Integrate with [[Build:TryServer]], to allow submitting a patch directly from Bugzilla | ||
* dolske: Integration with CVS/Hg and LDAP, so that users with checkin powers can do directly from Bugzilla (w/ checkin messages autogenerated). Future work could add warnings (or errors) if you're trying to checkin something without appropriate review and approval. And, vice versa, if something is checked into a repository without a corresponding bug. (-1) | * dolske: Integration with CVS/Hg and LDAP, so that users with checkin powers can do directly from Bugzilla (w/ checkin messages autogenerated). Future work could add warnings (or errors) if you're trying to checkin something without appropriate review and approval. And, vice versa, if something is checked into a repository without a corresponding bug. (-1) | ||
* bsmedberg: Remove most bug fields (severity/priority/target milestone/Hardware/OS/keywords/flags) with googlecode-style tags. Tags should be group-controllable like flags are currently. See [http://www.joelonsoftware.com/news/20020912.html Joel on Software] for why our fields hurt more than they help. | * bsmedberg: Remove most bug fields (severity/priority/target milestone/Hardware/OS/keywords/flags) with googlecode-style tags. Tags should be group-controllable like flags are currently. See [http://www.joelonsoftware.com/news/20020912.html Joel on Software] for why our fields hurt more than they help. (+1) | ||