I'd like to try and get some organization behind the labels we have on Github.
We've historically used them more like tags, trying to add anything the issue relates to. This doesn't scale well, since you have to flip back and forth to add labels on a separate page, and then they end up having 1 or 2 issues assigned to them because no one knows what labels there are so they don't bother. I'd like to see us cut the list down to some very basics, like 'critical', 'blocker', 'has_patch', 'needs_review', 'bug', 'enhancement', etc. Things that, in addition to milestone, would make it easy for us to glance at exactly what needs to be done for a release, what can easily be closed, etc. Things that we currently have as labels (or did before I just deleted several more) that don't fit well into the Github paradigm would include: date, flickr, il8n, pingback, pluggable, validation, viddler, xml. None of those have more than 1 or 2 issues assigned to them, which means they aren't inclusive enough to be truly useful, and they make it more difficult to find the ones we're actually looking for. Thoughts? -- -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev --- You received this message because you are subscribed to the Google Groups "habari-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
