Releasing Z2JH

[consideRatio]

@jupyterhub/jupyterhubteam I'd love to see a Z2JH release be made, so I'm reaching out for help to accomplish that. What's missing mostly is making releases of other dependent projects, so we can bump them in z2jh. If you have time to spare, I'd like your help to take these repositories towards a release!

z2jh dependency release checklist

• jupyterhub/configurable-http-proxy
  • Update CHANGELOG.md Update CHANGELOG.md for 4.2.0 configurable-http-proxy#221
  • Add RELEASE.md RELEASE.md documentation and small fixes configurable-http-proxy#220
• jupyterhub/jupyterhub
  There are many fixes available in JupyterHub master since last release, for z2jh one big is relating to stability on startup during simultaneous hub and proxy upgrades.
  • Update docs/source/changelog.md Changelog for 1.1.0 jupyterhub#2830
  • Add RELEASE.md (CHECKLIST-Release.md)
  • Get the docs update merged before JH release updating to pandas docs theme jupyterhub#2820
• jupyterhub/oauthenticator
  It is required for GitLab authentication fix that GitLab themselves would like to see included in Z2JH. They have made one click install of Z2JH in k8s clusters! I'm really eager to help them get this issue fixed.
  • OK to release, we can always make more releases later Make a release oauthenticator#299
  • Update CHANGELOG.md Add changelog for 0.10.0 oauthenticator#308
  • Add RELEASE.md Add RELEASE.md oauthenticator#294
  • Try making a release by pushing a git tag using @manics PyPI CD with TravisCI
  • Updating RELEASE.md for automatic releases.
• jupyterhub/kubespawner
  It contains a bugfix for k8s 1.16 among other things.
  • Review/Merge PR solving CI issues [MRG] CI reworked and bugs affecting tests fixed kubespawner#368
  • Review/Decide on a few PRs in need of review
  • Update docs/source/changelog.rst Update changelog for 0.11.0 kubespawner#372
  • Add RELEASE.md Add RELEASE.md and utilize bump2version kubespawner#376
  • Attempt to deploy PyPI package with CD following a push of a git tag, suceeded, see logs! Lesson learned that the test also run before. Perhaps we can tweak it so it becomes a pure deploy job without the test run also.
• jupyterhub/ltiauthenticator
  • Review / Merge lots of required PRs fixing issues blocking its inclusion in z2jh's hub image.
  • Make a release
  • Reinstall it into the z2jh hub image, where it currently has been deactivated because it's malfunctioning.

z2jh itself checklist

• Make a changelog - Update changelog for 0.9.0-beta.1 zero-to-jupyterhub-k8s#1503
• Bump jupyterhub a final time to whatever master we got or if a recent release is made
• Resolve Spawner event stream malfunctions :/ zero-to-jupyterhub-k8s#1501
• UPDATE: I don't consider this required for us to fix pre-release any more.
  Fix the core pod toleration bug - or feature, it is simply not added, that logic was stripped away from a past PR. Perhaps we don't need to fix this but it should at least be documented then.
  • Issue about it: Core pods (hub/proxy/autohttps/user-scheduler) doesn't get the hub.jupyter.org/dedicated=core:NoSchedule toleration zero-to-jupyterhub-k8s#1486
• Add support for environment variables mounted from secrets that arn't simply a key value pair
  • Current status documentation PR Added doc example of mounting k8s secrets as ENV variables to user pods without values.yaml zero-to-jupyterhub-k8s#1462
  • A discussion about it: A secrets friendly version of extraEnv zero-to-jupyterhub-k8s#1103

[choldgraf]

I agree it would be fantastic to get a new release out. Perhaps we can post this issue on the community forum as well?

[consideRatio]

@betatim i've now updated tasks of relevance and put in some work myself already. @manics shall we try making a release. Inspecting the PR lists of the repositories and helping me verify that it makes sense to make a release in the current state is relevant help for example.

[choldgraf]

Just a quick thought from me: it would be awesome if we could get the new documentation PR merged in /jupyterhub before a new release is made, since the documentation there is for stable/ by default, not latest/

[consideRatio]

Attention specifically to:

• KubeSpawner PRs in need of review and/or decisions: https://github.com/jupyterhub/kubespawner/pulls?q=is%3Apr+is%3Aopen+label%3A%22needs+review%22
• OAuthenticator PRs in need of review and/or decisions: https://github.com/jupyterhub/oauthenticator/pulls?q=is%3Apr+is%3Aopen+label%3A%22needs+review%22

[consideRatio]

I've made a release of oauthenticator now, and up comes kubespawner, and then we have jupyterhub itself left!

[consideRatio]

Review help request:

• Add RELEASE.md and utilize bump2version kubespawner#376
• Iteration of local development instructions kubespawner#377

I'll go ahead and release kubespawner after this using the @manics setup pattern to do PyPI CD by pushing a git tag.

It almost worked with oauthenticator, next try is with kubespawner :)

[consideRatio]

Kubespawner is now released and I got Z2JH to work on k8s 1.16, and I submitted PRs to fix binderhub for k8s 1.16 as well. See jupyterhub/binderhub#1012 and jupyterhub/binderhub#1013.

[consideRatio]

Prio to resolve: jupyterhub/zero-to-jupyterhub-k8s#1501

[consideRatio]

A jupyterhub release would be nice to reference, but nothing that should stop us from releasing alpha/beta of z2jh using current master instead. Most things have come around now.

[mjuric]

Apologies if this has an obvious answer, but does one of the recent alpha releases include the kubespawner with the jupyterhub/zero-to-jupyterhub-k8s#1501 fix?

(more generally, is there a way to quickly see which commits/releases of individual packages -- spawner, hub, etc -- went into each alpha-series Helm chart + hub images)?

[consideRatio]

No obvious answer, yepp the latest does for example!

We dont have a way to track dependencies for chart releases yet :/ it would be nice to have some pip freeze or similar provided someplace.

[consideRatio]

@mjuric you correctly identified a bug, it is resolved by jupyterhub/zero-to-jupyterhub-k8s#1518.

---

I also identified issues with the ltiauthenticator that needs to be solved, I made a few PRs to do so to the best of my ability, but there is one commit in jupyterhub/ltiauthenticator#26 that require a review by someone with more background understanding about the code base.

[consideRatio]

jupyterhub/litauthenticator issues resolved!

[consideRatio]

I'd be fine making a beta-release of z2jh - should we make it reference a jupyterhub beta release first or not?

[manics]

If the final z2jh release will include a new jupyterhub release I think it makes sense to tag a jupyterhub beta too and include it in the Z2JH beta, so that it gets some testing.

[consideRatio]

Z2JH 0.9.0 released 🌻

[consideRatio]

Upgrade instructions / changelog: https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/master/CHANGELOG.md#090---2020-04-15

[choldgraf]