-
Notifications
You must be signed in to change notification settings - Fork 54
Milestone
This will be renamed to the release tag near the time of the release. Any normally closed issues and pull requests should be marked against this milestone. If you are working on an issue and there is a good chance that it will make the release, you should move the issue to this milestone. You can also mark an issue on this milestone to block the next release.
The due date of this milestone will be continuously adjusted (1st working day of 1st full working week of each month?) so it is always around 2-3 months in the future. Top priority issues and easy fixes should be marked against this milestone. Issues that have been living in this milestone for more than 3 months but with no sign of activity will be moved to later.
Similar to soon, but with a due date adjusted to 1 year in the future. Medium priority issues and fixes that require some major work should be marked against this milestone.
The due date of this milestone is currently set to the end of 32-bit Unix time. Low priority issues and nice-to-have that require lots of efforts to implement should be marked against this milestone.
Please continue to delete the milestone for issues that are closed with duplicate, invalid or wontfix.
If 3 or more users request the same feature, then we should automatically consider raising the priority of the issue.