List view
- Due by May 8, 2026
- Due by May 8, 2026
- Due by May 8, 2026
- Due by May 8, 2026
- Due by May 8, 2026
- Due by April 10, 2026
- Due by April 10, 2026
- Due by April 10, 2026
- Due by April 10, 2026
MAYBE (probably not)
Overdue by 17 day(s)•Due by March 6, 2026•1/2 issues closed- Overdue by 17 day(s)•Due by March 6, 2026•1/9 issues closed
- Overdue by 17 day(s)•Due by March 6, 2026•1/9 issues closed
- Overdue by 17 day(s)•Due by March 6, 2026•1/9 issues closed
- Overdue by 25 day(s)•Due by February 26, 2026•9/9 issues closed
- Due by April 22, 2026
MAYBE - EOL is Feb 28 2026
Overdue by 25 day(s)•Due by February 26, 2026•3/3 issues closed- Overdue by 25 day(s)•Due by February 26, 2026•3/3 issues closed
- Overdue by 25 day(s)•Due by February 26, 2026•3/3 issues closed
- Overdue by 25 day(s)•Due by February 26, 2026•3/3 issues closed
- Overdue by 17 day(s)•Due by March 6, 2026•7/17 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•109/156 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