List view

• Next Release

  Tag issues as a way to emphasize that this is a high priority issue. The next release (or, in high pressure cases, the release after the next) should be blocked if a "Next Release" milestone issue is open.

  No due date

  •4/5 issues closed
  80% complete1 open4 closed

• 1.1

  No due date

  •11/24 issues closed
  45% complete13 open11 closed

• 1.0

  Bugs needed to be finished before our first stable release Of course, this includes MVP functionality (see issue #1), but we should decide to allow additional bugs in if 1. They have a high likelihood of being used across many projects 1. The feature complexity is O(days), *maybe* O(2 weeks) 1. They are features we want to figure out earlier than later, because they'll affect later desig 1. They are bugs which block users from deploying sites using this framework

  No due date

  •113/158 issues closed
  71% complete45 open113 closed