-
Notifications
You must be signed in to change notification settings - Fork 33
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.
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
Overview of release planning #650
Comments
@minrk @GeorgianaElena @manics I've mentally planned that oauthenticator 16 should be released and bundled with z2jh 3 and tljh 1, but I think we should perhaps go for another major release of z2jh/tljh when oauthenticator 16 arrives instead. What do you think? If so, I think z2jh 3 and tljh 1 can be released, which also helps the pending binderhub 1 release get z2jh 3 in it. |
I haven't been on top of the oauthenticator 16 plans, but I trust you and this sounds fine to me. Preparing to release one thing shouldn't in general put too much pressure on upstream or downstream packages to release. |
@consideRatio, I can get jupyterhub/oauthenticator#594 updated tomorrow, which I believe it's the last major bit that we planned to go into |
Are there plans for cutting a new 4.0.x anytime soon? It looks like a number of backports (some more exciting than others) have landed since 4.0.2 :) |
Yes, those backports are in preparation for 4.1 soon. I'm working on one remaining issue before cutting the release. |
JupyterHub 4.1.0, oauthenticator 16.3.0, and z2jh 3.3.0 was released today |
Closing as resolved |
With JupyterHub 4 released, the distributions z2jh and tljh benefits from a release as well, and when they are to make a breaking release I figure its also nice to have up to date versions of other projects they depend on, such as kubespawner, oauthenticator, etc.
Tracked major version releases
allowed_users
,admin_users
, _or_ other allowed/admin groups oauthenticator#594Tracked minor/patch version releases
The text was updated successfully, but these errors were encountered: