Skip to content

Milestones

List view

  • No due date
    6/7 issues closed
  • No due date
    55/60 issues closed
  • An issue that touches things that are online, like the README or website, and therefore can't really be tied to a *release*.

    No due date
    20/22 issues closed
  • This milestone is applied when an issue is closed because the decision is the requested change will not be implemented. This typically happens on enhancement requests where the requested behavior is not compatible with the fish project goals, or is otherwise not practical or desirable. This milestone exists to make it easy to distinguish proposed changes we will never implement from those that might appear in a future release.

    No due date
    792/793 issues closed
  • Fixes that break backward compatibility must be targeted to this release.

    No due date
    0/7 issues closed
  • These are issues that are not targeted for an upcoming minor or major release. After a release, we will re-examine these issues and pull any in that we think are good targets; that is retarget them to the next minor (or major) release. If you can provide a fix for an issue in this milestone, we'll generally accept it for the next release even if the issue is not targeted for the release.

    No due date
    5/365 issues closed