List view

• next-major

  Issues that involve non-backward compatible changes should be assigned to this milestone.

  No due date

  •1/1 issues closed
  100% complete0 open1 closed

• next-minor

  Assigned to bugs and enhancement requests that should be targeted for the earliest possible release. These by definition cannot introduce backward incompatible behavior or ABI changes. Such issues should be assigned to the `next-major` milestone.

  No due date

  •10/11 issues closed
  90% complete1 open10 closed

• will-not-fix

  This milestone should be assigned when closing an issue that will not be addressed. Typically because the requested change is not compatible with the project goals or is infeasible in any practical sense. For example, asking that a ksh JIT compiler be implemented. That's the sort of feature that could only be implemented if a major corporation decided to play a major role got involved.

  No due date

  •21/21 issues closed
  100% complete0 open21 closed