Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Release planning for v2 #991

Open
31 tasks done
consideRatio opened this issue Sep 4, 2024 · 5 comments · May be fixed by #1010
Open
31 tasks done

Release planning for v2 #991

consideRatio opened this issue Sep 4, 2024 · 5 comments · May be fixed by #1010
Labels
maintenance

Comments

@consideRatio
Copy link
Member

consideRatio commented Sep 4, 2024 •
edited
Loading

I'd like to work towards a v2 release with jupyterhub 5 and oauthenticator 17.

Todo
@consideRatio consideRatio pinned this issue Sep 4, 2024
@minrk
Copy link
Member

minrk commented Sep 4, 2024 •
edited
Loading

24.04 is already in the test matrix, and JupyterHub 5 is done in #989

@minrk minrk mentioned this issue Sep 4, 2024
Merged
@consideRatio consideRatio mentioned this issue Sep 12, 2024
Merged
@minrk
Copy link
Member

minrk commented Sep 17, 2024

I want to try to put a lot less pressure on other projects when we prepare a release like this. I feel strongly that we should at most check if a project is "due" for a release and do no more coordination than that. Deciding that a distribution is ready for release should ideally not create time-pressured work in other repos. If they aren't ready or approximately ready to release when it's time to make a distro release, they shouldn't be in the distro release.

@consideRatio's been doing a lot of great work refreshing projects like ldapauthenticator, but I also want to make sure that work like that is not considered part of the release process for tljh or z2jh (i.e. I'm definitely not saying the work shouldn't be done, but it shouldn't be expected when another project is preparing a release, and typically shouldn't block a downstream release).

This was referenced Sep 4, 2024
Closed
Merged
@consideRatio
Copy link
Member Author

I went for 2.0.0b1

https://discourse.jupyter.org/t/the-littlest-jupyterhub-tljh-distribution-2-0-0b1-beta-1-is-out/28822

@consideRatio
Copy link
Member Author

consideRatio commented Oct 18, 2024 •
edited
Loading

JupyterHub 5.2.0 seem to cause issues for tljh, as reported in the CI system here: https://github.com/jupyterhub/the-littlest-jupyterhub/actions/runs/11410693112.

I've pinned it to 5.1.0 for now via #1007, but we should have this debugged and resolved before release of v2.

@consideRatio
Copy link
Member Author

JupyterHub 5.2.0 now functions, with systemdspawner 1.0.2 bugfix release, fixed in #1008.

@consideRatio consideRatio linked a pull request Oct 20, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
maintenance
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add changelog for 2.0.0 consideRatio/the-littlest-jupyterhub
2 participants
@minrk @consideRatio