Trac field: branches
Document Actions
Submitted by
jccooper.
on 2007-07-05 13:01.
As if we don't have enough, I think maybe we need one more field in the bug system: branches.
If we're going to use the same bug tracker for in-development bugs and production bugs, we really ought to be able to separate them nicely. The 'component' field obviously doesn't do it, and the milestone field might, except it seems to be being used for other purposes (and milestones could legitimately want some live bugs fixed and some branches merged.)I propose a 'branches' or 'devset' field, which would specify exactly where the problem code is, or where it should be fixed. The values would be 'trunk' or None or something, and whatever active devsets or branch sets we happen to have. People working on a branch would then be able to nicely filter in-dev bugs (useful for both development and testing, I think) and reports would be able to ignore all the development bugs, which aren't a real quality impact issue.
