List view
- Due by June 30, 2025
- Due by May 31, 2025•5/5 issues closed
- Due by April 30, 2025•4/4 issues closed
- Due by April 4, 2025•9/9 issues closed
Milestone Owner: @dcmcand This milestone includes the PRs that will be included in the 2025.3.1 release
Due by March 14, 2025•8/8 issues closedRelease focused on improvements to Test suite, Release process, and stability.
Due by February 28, 2025•5/5 issues closed- Due by December 15, 2024•18/18 issues closed
The focus of the November 2024 increment for the Nebari Maintenance Team will be: Improvements to Nebari cost controls Cleaning up the Pydantic models in order to improve the developer experience and make generation of documentation easier Dependency updates. Specifically JupyterHub, Conda-Store, Argo Workflows and Keycloak Addressing Security Issues Improvements to CI speed and reliability
Due by November 30, 2024- Due by November 8, 2024•10/10 issues closed
~This is a milestone with all the items we want to include in the 2025.1.1 release~ Superseded by 2025.2.1
Due by January 31, 2025•14/14 issues closedTentatively planned to be released in October 2024
No due dateMilestone to track what tests are needed to more fully automate releases
No due dateIssues that the Nebari Maintenance team is planning on working on, but is not in the current increment.
No due date•3/3 issues closedThe focus of the September 2024 increment for the Nebari Maintenance Team will be: 1. Improvements to Nebari cost controls 2. Cleaning up the Pydantic models in order to improve the developer experience and make generation of documentation easier 3. Dependency updates. Specifically JupyterHub, Conda-Store, Argo Workflows and Keycloak 4. Addressing Security Issues 5. Improvements to CI speed and reliability
Due by September 30, 2024•11/11 issues closed- No due date•6/6 issues closed
- No due date
- No due date•9/9 issues closed
- No due date•5/6 issues closed
- No due date•9/9 issues closed
- No due date•8/8 issues closed
- No due date•2/3 issues closed
- No due date
- No due date•4/5 issues closed
- No due date•1/2 issues closed
- No due date•1/2 issues closed
Planning to cut an RC the week of 2024-09-16
Due by September 27, 2024•12/12 issues closed- Due by April 15, 2024•9/9 issues closed
- Due by March 25, 2024•18/18 issues closed
- Update K8s support to 1.29 - Add new conda store release (2024.3.1)
Due by March 31, 2024•7/7 issues closed- No due date•6/8 issues closed
- No due date•12/12 issues closed
- Due by December 22, 2023•5/5 issues closed
- No due date•23/23 issues closed
*Tentative milestone for November release.*
Due by November 21, 2023•13/13 issues closedRelease for October 2023. This includes the extension-mechanism refactor.
Due by October 20, 2023•43/43 issues closedPotential June 2023 release milestone.
Due by July 6, 2023•5/5 issues closedPotential May 2023 release.
No due date•11/12 issues closedApril 2023 release.
No due date•5/5 issues closedMarch 2023 release.
No due date•11/11 issues closedJanuary 2023 release.
Due by January 24, 2023•11/11 issues closedNovember 2022 release.
Due by November 30, 2022•6/6 issues closed- Due by October 28, 2022•29/29 issues closed
- No due date•10/10 issues closed
- No due date•3/3 issues closed
- No due date•21/21 issues closed
Hotfix for: https://github.com/Quansight/qhub/issues/1319
Due by June 8, 2022•5/5 issues closed- No due date•16/16 issues closed
This milestone is a placeholder for longer-term goals and objectives that have not yet been assigned to a concrete milestone. The general pattern: - version X is the latest release - version X+1 has a milestone - PRs added to this milestone _should_ be included in version _X+2_, once a milestone has been created for it
No due date•26/33 issues closedReserved for: - minor bug fixes that don't impact API surface - minor doc / release note updates
Due by April 4, 2022•6/6 issues closed- Bugfixes and stability improvements - UI improvements - JupyterLab profiles integrated with Keycloak
Due by May 9, 2022•21/21 issues closed