Milestones
List view
May happen, may not happen, we shall see
No due date•6/6 issues closed- No due date•39/39 issues closed
- No due date•840/840 issues closed
- No due date•17/17 issues closed
- No due date•14/15 issues closed
- No due date•518/518 issues closed
- No due date•27/27 issues closed
- No due date•101/101 issues closed
- No due date•9/9 issues closed
- No due date•977/977 issues closed
- No due date•21/21 issues closed
- No due date•18/18 issues closed
- No due date•91/91 issues closed
- No due date
- No due date•9/9 issues closed
- No due date•6/6 issues closed
- No due date•2/2 issues closed
- No due date•700/701 issues closed
tracker for any issues that would prompt a release on the 2.18 stable branch
No due date•23/23 issues closedIdeally we release 2.18 but can queue things here
No due date•17/17 issues closed- No due date•6/6 issues closed
- No due date•10/10 issues closed
- No due date•17/17 issues closed
- No due date•16/17 issues closed
- No due date•410/410 issues closed
Step 1: verify issue still reproduces w/new backend in 2.17. Close if can't reproduce Step 2: verify it is a regression from 2.16.5. Can move to 2.18 release milestone if it is not a regression Please add comment with findings and set milestones accordingly That will get a 2.17 release that does not regress from 2.16.5 as fast as possible
No due date•920/920 issues closedIssues which are resolved when we enable the Rust Backend This issue acts as a holding pen for issues which are resolved by the Rust Migration. As the Rust Migration isn't tied to a specific release, we want to keep these separate from the standard versioning milestones. Once we decide when the Rust Migration will go live, all issues in this milestone will be transferred to the appropriate version milestone
No due date•14/14 issues closedThere are no current plans to release a 2.15.7, there is a preference for releasing 2.16.0 But this milestone may collect issues that are cherry-pickable in case we do a 2.15.7 release
No due date•4/4 issues closedThis is unplanned - there are no plans for 2.15.6, only creating the milestone in case there is an emergency type fix needed for 2.15.5. Hopefully this milestone remains empty and is closed.
No due date•2/2 issues closed- No due date•29/29 issues closed
I'd prefer to get 2.16.0 out more quickly, but 2.15.4 is always a possibility
No due date•2/2 issues closed- No due date•41/41 issues closed
- No due date•8/8 issues closed
- No due date•13/13 issues closed
- No due date•3603/3603 issues closed
There is no expectation we will release a 2.14.4 but it is our current stable branch so this milestone exists to collect things just in case.
No due date•6/6 issues closed- No due date•8/8 issues closed
- No due date•26/26 issues closed
- No due date•23/23 issues closed
- No due date•652/652 issues closed
No plans to release this but it is here to for issue tagging in case it is needed
No due date- No due date•11/11 issues closed
Further releases on 2.13 stable series may not be needed, but I always create a stub entry for stable tree just in case.
No due date•15/15 issues closed- No due date•7/7 issues closed
- No due date•12/12 issues closed
- No due date•10/10 issues closed
- No due date•399/399 issues closed
- No due date
- No due date•5/5 issues closed
- No due date•266/266 issues closed