List view

• v3-future

  Issues that should be completed after the v3.0.0 major release, i.e. issues not planned for the initial v3.0.0 release.

  No due date

  •0/20 issues closed
  0% complete20 open0 closed

• v3-rc

  Goal: Address outstanding v3 bugs before the official v3.0.0 release. After this milestone is complete, we can cut the **v3.0.0** major release and begin working on the `v3-future` milestone.

  No due date

  •3/15 issues closed
  20% complete12 open3 closed

• v3-alpha

  Goal: Establish new v3 APIs and allow for feature parity with v2. This does not include all of the features we want to add, but implements the APIs required by those features. Once this milestone is complete, a v3.0.0b0 release should be published.

  No due date

  •7/7 issues closed
  100% complete0 open7 closed

• Priority

  Issues with a great reward-to-effort ratio that should be prioritized as "easy wins" by other contributors.

  No due date

  •7/7 issues closed
  100% complete0 open7 closed

• v3-beta

  Goal: Add new major features using v3 API, enhance UX. After this milestone is complete, we can cut a **v3.0.0rc0** release and begin working on the v3-rc milestone.

  No due date

  •17/25 issues closed
  68% complete8 open17 closed

• Future

  No due date

  •9/28 issues closed
  32% complete19 open9 closed