zero-to-jupyterhub-k8s
zero-to-jupyterhub-k8s copied to clipboard
jupyterhub
docs: add changelog for 2.0.0
DRAFT: This has to be updated to include a lot of changes that has arrived over time since it was created.
:wave: Hi, I'm currently on 1.2.0 and am just trying to figure out when 2.0.0 will be released.
Are there any concrete plans to release 2.0.0 imminently? Is there a better issue or place I can track progress?
Needs to be done
Here are things I'd like to see done before we agree to merge a changelog and cut a release that I can quickly name from the top of my head.
- [x] #2508, I need to document this properly enough (this is on me)
- [x] Triage most PRs and issues was something I wanted to do as well (resolved now)
- [x] This changelog needs to document/link out well enough the breaking changes in kubespawner and elsewhere (help appreciated)
@manics :heart: :tada: :rocket: thanks for pushing onwards!!!
Feel free to push commits directly if you want btw!
If we want to begin pre-testing the 2.x release while waiting for the last items related to changelogs, where would we find that chart?
@consideRatio I've merged in main (to bring in the new upgrade-1-to-2.md guide) and removed the relevant sections from the changelog. I think we should squash all these commits before merging.
@consideRatio I think I've added all the missing PRs so this should be up to date now.
I've changed the version to 2.0.0-beta.1, this takes some of the pressure associated with a final 2.0.0 release. Do you think this is ready to go?
I've rebased and squashed all commits into one here, in case you want to force push it to this PR: ~https://github.com/manics/zero-to-jupyterhub-k8s/commit/afe5d1d192ed605cb4ad1ed8fd0cb1dbf3200100~ https://github.com/manics/zero-to-jupyterhub-k8s/commit/d01f3d63c479dc4227ae50d403a8fc5ba091d67c
At risk of delaying this further, the next release of JupyterHub requires another DB upgrade, so maybe we should wait? https://github.com/jupyterhub/jupyterhub/issues/3982
At risk of delaying this further, the next release of JupyterHub requires another DB upgrade, so maybe we should wait? jupyterhub/jupyterhub#3982
To me, this seems a good reason not to delay. Users can get an awesome new version now without having to upgrade the db. Unless I'm misunderstanding.
Yup, JupyterHub 2 has a big, disruptive DB upgrade requiring everything to shutdown and restart. JupyterHub 3 has a db upgrade that z2jh users running the default sqlite shouldn't even notice.
I'm not necessarily opposed to pulling in JupyterHub 3, but if we do that, I'd like to try to focus on reviewing hub 3.0 release PRs. As far as I'm concerned, everything's ready to go but the changelog and I could make a 3.0 beta today: https://github.com/jupyterhub/jupyterhub/pull/3994 . But I don't want to self-merge too much over there.
What do folks think about testing https://github.com/jupyterhub/chartpress/pull/150 during the 2.0 prerelease cycle? (note: does not need to be picked up before making the first 2.0 beta)
@manics @minrk @sgibson91 - should we go for a release with this? I've updated the PR entries etc so far. The changelog entry can be reviewed in https://zero-to-jupyterhub--2528.org.readthedocs.build/en/2528/changelog.html.