Milestones
List view
Issues I'm not yet sure about. May or may not be a good idea, worthwhile, etc.
No due date•0/2 issues closedIssues that have yet to scheduled, and likely yet to be scoped and triaged, but that seem like a good idea.
No due date•0/9 issues closedRefer to (my blog article on how I use GitHub issues)[http://peter-whittaker.com/How-I-use-GitHub-Issues/]: Next[ABC] are used to manage dependencies between issues that share a la bel - NextA should be done before NextB before NextC. Note that Next means "do these next" while "Next[ABC]" mean "do in this order". (Perhaps t hese should be renamed to "Order[ABC]".
No due dateRefer to (my blog article on how I use GitHub issues)[http://peter-whittaker.com/How-I-use-GitHub-Issues/]: Next[ABC] are used to manage dependencies between issues that share a la bel - NextA should be done before NextB before NextC. Note that Next means "do these next" while "Next[ABC]" mean "do in this order". (Perhaps t hese should be renamed to "Order[ABC]".
No due date•0/2 issues closedRefer to (my blog article on how I use GitHub issues)[http://peter-whittaker.com/How-I-use-GitHub-Issues/]: Next[ABC] are used to manage dependencies between issues that share a label - NextA should be done before NextB before NextC. Note that Next means "do these next" while "Next[ABC]" mean "do in this order". (Perhaps these should be renamed to "Order[ABC]".
No due date•0/2 issues closedIssues to be worked on next. These should have been triaged and scoped, with half-decent descriptions.
No due dateIssues that can be done anytime. Generally small in scope, LHFs (low-hanging fruit).
No due date•0/3 issues closed