severity for git issues

[Dr. Micah Altman]

Previously we had TRAC configured to enter severity and to distinguish RFE's from bugs. Should we set something up to do this w the git issue tracker as well? Is there a preferred mechanism?

[Andrew Jennings]

GitHub doesn't have a severity item for issues but they have a flexible tag system.  I'll add some priority tags.  We already have a "wishlist" in there.  I'll put a "bug" and a "confirmed" in there, too, to make for easy searching for those times when we just have a few minutes for bug-squashing.   I think the usual 7-priority system is too much so how about: "critical fix", "high priority", "low priority".  Is that too simple?  We've been assigning areas to the tasks we're creating; those can certainly be applied to bugs, too.

Any other comments / recommendations ideas about tags?

- Andrew

[Dr. Micah Altman]

Sounds good to me. - Micah 

--
________________________________________________________________________
Micah Altman, Ph.D. <http://redistricting.info>           Twitter: @drmaltman   
Senior Research Scientist, Institute for Quantitative Social Science, Harvard U.
Archival Director, Henry A. Murray Archive;
"Entia non sunt multiplicanda sine necessitate" - Dr. Invincibilis (Corollary, "Ad indicia spectate.")

[Andrew Jennings]

Done.

- Andrew