Planning for release 1.0.0

[consideRatio]

This is a placeholder PR to track work towards the 1.0.0 release, maintainers please feel free to edit this!

Blocking issues/PRs

• Update base user environment to mambaforge 23.1.0-1 (Python 3.10) #858
• Add upgrade test from latest release and from previous major version's latest release #868
• update: jupyterhub 4 #880
• Remove jupyterhub-configurator in 1.0.0? #901
• Update systemdspawner from version 0.17.* to >=1.0.1,<2 #915
• Test logs from tests extremely hard to read #899
• Upgrade from 0.2.0 fails (because a corrupt conda/mamba file?) #918
• --force-reinstall old conda to ensure it's working before we try to install conda packages #920
• Release planning for 16.0.0 oauthenticator#585
• breaking: update oauthenticator from 15.1.0 to >=16.0.2,<17, make tljh auth docs link out #924
• Add changelog for 1.0.0b1 #888
• There be notes to link to from the changelog on how to make an upgrade and what to think about when doing one
  • Document upgrade strategy #81

Relevant but maybe not blocking issues/PRs

• Proposal to minimize what TLJH installs in the user environment #872
• Upgrade to jupyterhub 4? #874
• Review public/private methods and classes #909

Helpful notes for creating the changelog

Can we upgrade straight from jupyterhub 1 to jupyterhub 4?

It's tested in the jupyterhub suite and should be supported. It's a disruptive upgrade (the 1->2 transition means all user servers must be restarted and any API-issued tokens will be revoked), but for most tljh use cases, the restart-everything should be the only issue folks need to deal with.

[consideRatio]

I moved #872 to blocking at least pending further discussion as I currently don't want pip install --upgrade of requirements-base.txt to cause issues in the user environment that is unrelated to making the jupyterhub itself function.

[nsurleraux-railnova]

Hi @consideRatio,

First, I would like to say thank you for the amazing work on TLJH. Without wanting to be pushy, is there an ETA on 1.0.0 release? We would need to have JupyterHub>=4.0 for JupyterLab extensions to be picked up correctly (see jupyter-server/jupyter-scheduler#370). If there are any known workaround in the meantime, I would highly appreciate it.

Thanks !

[consideRatio]

@nsurleraux-railnova with the disclaimer that its not something I can estimate well, I can say that I will do what I can to get a release out in a month.

[consideRatio]

@nsurleraux-railnova a pull request to add the changelog for 1.0.0 is opened and ready for review, you are most welcome to provide feedback on the text if you want!

[consideRatio]

A beta release is out, check the changelog for details. At this point what remains is feedback about using the beta and documentation on how to upgrade in general.

The changelog is available at https://tljh.jupyter.org/en/latest/reference/changelog.html

[godber]

Will this 1.0 release include JupyterLab 4 and Jupyter Notebook 7, both of which recently released.

BTW, I was able to upgrade from the current latest to the 1.0.0.b1 on a small install with no problem, I had to restart the upstream reverse proxy for some reason, but it was fine after that.

[jtpio]

FYI #928 updates to Notebook 7 and JupyterLab 4.