List view
- Due by February 6, 2026
- Due by February 6, 2026
- Due by February 6, 2026
- Due by February 6, 2026
- Due by February 6, 2026
- Due by January 9, 2026
- Due by January 9, 2026
- Due by December 17, 2025
- Due by January 9, 2026•0/1 issues closed
- Due by January 9, 2026•0/1 issues closed
- Due by January 9, 2026•0/1 issues closed
- Overdue by 4 day(s)•Due by December 5, 2025•0/10 issues closed
- Overdue by 4 day(s)•Due by December 5, 2025•1/3 issues closed
- Overdue by 4 day(s)•Due by December 5, 2025•1/3 issues closed
- Overdue by 4 day(s)•Due by December 5, 2025•1/3 issues closed
- Overdue by 4 day(s)•Due by December 5, 2025•1/4 issues closed
This milestone represents issues that are less critical, but we would like to keep on our radar and work on if possible. Items in the milestone are not being actively worked on. If we plan to start on them, they’ll be moved to a version milestone like “1.20 - Backlog”.
No due date•108/154 issues closedThis is a long-lived milestone that will capture documentation issues that are not tied to a particular release.
No due date•43/44 issues closed