You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jupyter Notebook v7 is going to be released relatively soon, and when this happens, it will create some confusion for JupyterHub administrators that are not pinning their versions to v6 (which I suspect very few are doing). There are some conversations around ways to mitigate the pain here. For example:
However, most hub administrators will likely still need to take some kind of action to prepare their hubs for the switch.
Proposal
We should create a short blog post with guidance for hub administrators, to help them understand what to expect and what needs to be done with Notebook v7. I think this should be a blog post, because it is the most high-visibility Jupyter communications space, and will be seen by the most people. We can also use this guide to identify pain points and design potential technical solutions around them.
Things that a guide should contain
Here are a few things that we should note:
nbgitpuller links. If a person was sharing nbgitpuller links that used the notebook interface, what will happen when notebook v7 is released, if they used content that assumed notebook v6 extensions? We agreed that old nbgitpuller links should be expected to still work, and should document/solve this.
using both v6 and v7 simultaneously. Many hub communities will not be able to "just switch" to notebook v7, and we don't want to encourage a practice of communities just hard-pinning to notebook v6. For this reason, we all agreed it is important to make it possible for both the classic interface, and the v7 interface to be installed in the same environment. There's an issue discussing this here: Educational JupyterHub considerations for notebook v7 switch jupyter/notebook-team-compass#10
If we are missing any other "gotchas" that will likely pop up, please suggest them here and we can add it in!
The text was updated successfully, but these errors were encountered:
Context
Jupyter Notebook v7 is going to be released relatively soon, and when this happens, it will create some confusion for JupyterHub administrators that are not pinning their versions to v6 (which I suspect very few are doing). There are some conversations around ways to mitigate the pain here. For example:
However, most hub administrators will likely still need to take some kind of action to prepare their hubs for the switch.
Proposal
We should create a short blog post with guidance for hub administrators, to help them understand what to expect and what needs to be done with Notebook v7. I think this should be a blog post, because it is the most high-visibility Jupyter communications space, and will be seen by the most people. We can also use this guide to identify pain points and design potential technical solutions around them.
Things that a guide should contain
Here are a few things that we should note:
If we are missing any other "gotchas" that will likely pop up, please suggest them here and we can add it in!
The text was updated successfully, but these errors were encountered: