Communicate the upcoming Notebook 7

[echarles]

This is an umbrella issue to discuss how we should communicate about the upcoming Notebook 7 release and the impacts for the existing NbClassic users.

Action	Timeline	Detail	Status
NbClassic Banner	ASAP	Read the migration plan to Notebook 7 to learn about the new features and the actions to take if you are using extensions	Done
Notebook 6.5 Banner	ASAP	Read the migration plan to Notebook 7 to learn about the new features and the actions to take if you are using extensions	Done
Notebook 7 migration RTD	ASAP	On notebook latest RTD - Pointer from other RTD	Done
Notebook 7 migration Blog 1	T0 - 2 weeks	TLDR of upcoming Notebook 7 RTD
JupyterLab 4.0.0 Release	T0
Notebook 7.0.0 Release	T0 + 2 months	Minimum 2 months, with at least a patch release of JupyterLab 4
Notebook 7 migration Blog2	T0 + 2 months	Notebook 7 release features & excitement, mention of Blog 1 for further background

The documented migration plan should cover:

• An explanation of the move from Notebook 6 to Notebook 7, highlighting the most important changes, maybe a bit of a re-summarization of JEP79 that provides updated information on standing of the various frontends (including a brief explanation of NbClassic, and links to NbClassic RTD).
• Include list/link to list of classic Notebook extensions that have been ported and those popular extensions that are yet to be ported/are WIPs.

[echarles]

@jupyter/notebook-council We have just proposed during today notebook community call to discuss on the sequence of events related to nbclassic and notebook communication/release sequence.

[ellisonbg]

I wasn't able to make it, can someone summarize the dicussion here?

On Wed, Feb 8, 2023 at 9:04 AM Eric Charles @.***> wrote:

@jupyter/notebook-council https://github.com/orgs/jupyter/teams/notebook-council We have just proposed during today notebook community call to discuss on the sequence of events related to nbclassic and notebook communication/release sequence.

— Reply to this email directly, view it on GitHub https://github.com/jupyter/nbclassic/issues/214#issuecomment-1422951410, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAGXUAKXP3V7JE5ZE337WDWWPGYZANCNFSM6AAAAAAUOYFFBY . You are receiving this because you are on a team that was mentioned.Message ID: @.***>

-- Brian E. Granger

Senior Principal Technologist, AWS AI/ML @.***) On Leave - Professor of Physics and Data Science, Cal Poly @ellisonbg on GitHub

[echarles]

We have proposed to show a message in a banner and the startup log for nbclassic and notebook 6.5 (not notebook 6.4). The content of that message needs to be defined (personally, I have highlighted the need to find the correct balance between inviting users to migrate and informing them they may break extensions they are using).

On top of that banner/log action, it has become clear that other actions are needed like writing a blog post, defining the unique RDT location where the details and impact of that migration will be explained. We said also a blog post on the Jupyter blog will be usefull.

We did not have time to discuss in detail the needed time between Notebook 7 and JupyterLab 4 release.

The goal is thus to discuss and define concrete and planned actions for the above points here (I will try to list some actions in a table format by tomorrow).

[echarles]

I have updated the description of this issue with a proposal.

[RRosio]

I wanted to share some thoughts here as I read through these updates...

Notebook 6.5 Banner and NbClassic Banner:

• I appreciate that the details for the banner encourage extension users/devs to have a closer look at documentation. It seems that this strikes more of a balance between sharing excitement for Notebook 7 and sharing the considerations extension users may need to make. As for the documentation that would be linked here, I also like the idea that this documentation live with Notebook 7 and am hoping that it can touch on a few points:
  • An explanation of the move from Notebook 6 to Notebook 7, highlighting the most important changes, maybe a bit of a re-summarization of JEP79 that provides updated information on standing of the various frontends (including a brief explanation of NbClassic, and links to NbClassic RTD).
  • Include list/link to list of classic Notebook extensions that have been ported and those popular extensions that are yet to be ported/are WIPs.

In terms of blogging content, I thought it might work well as a two part series along the lines of:

• Blog 1 -> TLDR of Notebook latests (7) RTD
• Blog 2 -> Notebook 7 release features & excitement, mention of Blog 1 for further background

I am not someone accustomed to releasing software to such a large community. So from my perspective it seems like a good idea to have some time in between the release of Jupyterlab 4 and Notebook 7. From the last notebook call, it seemed the most resonating answer to the benefit of releasing Notebook 7 almost immediately upon releasing Jupyterlab seemed to be the impact that a simultaneous release would have. My question here for my learning would be if someone could share some additional benefits they see in a closer release of the two projects? Maybe the pros and cons and how impact is weighted among those?

[echarles]

Thx @RRosio I have updated the initial comment with your suggestions.

[echarles]

@jupyter/notebook-council I hope we can land a decision during tomorrow community meeting on the proposed plan so we can merge the banner/log PR, push the documentation and cut a nbclassic release. The sooner we cut that nbclassic release, the more time users will have to anticipate and prepare the migration.

[andrii-i]

@echarles I'd add explicit warning that update to Notebook 7 might break some extensions. Rationale is that some people would only read the popup and we need to explicitly warn them about breaking changes on top of inviting them to learn more. Something like:

"Read the migration plan to Notebook 7 to learn about the new features and the actions to take if you are using extensions. Please note that updating to Notebook 7 might break some of your extensions."

[echarles]

@andrii-i Thx, makes sense to me. I can update the PR in that way if others here are OK with that udpate.

[jtpio]

Closing as Notebook 7 has now been released: https://blog.jupyter.org/announcing-jupyter-notebook-7-8d6d66126dcf