Release planning for v2

[consideRatio]

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

Todo

• Update base user environment to miniforge 24.7.1-0 (Python 3.12) #990
• Test and verify function against ubuntu 24.04
  • Integration tests
  • Unit tests: ci: run unit tests in ubuntu-24.04 github actions environment as well #993
• Transition to jupyterhub 5 (jupyterhub 5 #989)
• Transition to oauthenticator 17
  • Note that oauthenticator[azuread]>=16.0.4,<17 is installed, but we no longer need to specify azuread I think. Look it up in oauthenticator.
  • update oauthenticator to 17 #992
• Consider getting a release out for:

  • jupyterhub-systemdspawner>=1.0.1,<2

    • Ensure tests for jupyterhub 5 etc pass and refresh CI system things
      ci: test jupyterhub 5, python 3.12, ubuntu 24.04 systemdspawner#143
    • No merged PRs, not aiming for a release.

  • jupyterhub-firstuseauthenticator>=1.0.0,<2

    • Ensure tests for jupyterhub 5 etc pass and refresh CI system things
      ci: refresh github workflows firstuseauthenticator#57
      default: allow all users if allowed_users is unspecified firstuseauthenticator#56
    • Make release, a PR related to jupyterhub 5 is merged.
      Add changelog for 1.1.0 firstuseauthenticator#58

  • jupyterhub-nativeauthenticator>=1.2.0,<2

    • Ensure tests for jupyterhub 5 etc pass and refresh CI system things
      Require jupyterhub 4.1.6+ and Python 3.9+ nativeauthenticator#274
    • Fix a bug: Fix user was added on sign-up even if password didn't match confirmation nativeauthenticator#275
    • Make release, things have happened since last.

  • jupyterhub-ldapauthenticator>=1.3.2,<2

    • Ensure tests for jupyterhub 5 etc pass and refresh CI system things
      ci: test jupyterhub 5 and python 3.12, refresh github workflows ldapauthenticator#244
      Require jupyterhub 4.1.6+ and Python 3.9+ ldapauthenticator#245
      Fix broken tests for jupyterhub 5 ldapauthenticator#246
    • Make release of v2.0.0
      • Add changelog for 2.0.0b1 ldapauthenticator#272
      • Add changelog for 2.0.0b2 ldapauthenticator#285
      • Release plan for 2.0.0 ldapauthenticator#220

  • jupyterhub-tmpauthenticator>=1.0.0,<2

    • Ensure tests for jupyterhub 5 etc pass and refresh CI system things
      ci: test against jupyterhub 5 and refresh workflows tmpauthenticator#65
    • No release needed, nothing merged of relevance.

  • jupyterhub-idle-culler>=1.2.1,<2

    • Ensure tests for jupyterhub 5 etc pass and refresh CI system things
      ci: test against jupyterhub 5 jupyterhub-idle-culler#80
    • Make release, a new feature was added.
      Add changelog for 1.4.0 jupyterhub-idle-culler#81
• Update lower bounds on all stuff above
• Consider working the following open PRs through the finish line or closing them
  • Add locale and other environment variables support for systemd service jupyterhub #414
  • Specify user-environment Python version #784
  • Add the ability to define conda channels in plugins via tljh_extra_user_conda_channels #942
  • Add TLJH config lockfile #976
• Update to use traefik-proxy v2
  jupyterhub/traefik-proxy v2 is out, we should bump to use it! #996
• make changelog link to upgrade docs
• Add Test upgrade from 1.* #1003 to the changelog, which wasn't captured in the 2.0.0b1 release
• Do a final 2.0.0 release of ldapauthenticator and bump here

[minrk]

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

[minrk]

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).

[consideRatio]

I went for 2.0.0b1

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