readme: link to v6 plan

This commit is contained in:
Eric Charles 2022-04-26 10:28:57 +02:00
parent 20ba48b1b1
commit 868c9b9b61

View File

@ -14,7 +14,9 @@ computing.
The Jupyter Notebook project is currently undertaking a transition to a more modern code base built from the ground-up using JupyterLab components and extensions.
There is new stream of work which was submitted and then accepted as a Jupyter Enhancement Proposal (JEP): https://jupyter.org/enhancement-proposals/79-notebook-v7/notebook-v7.html
There is new stream of work which was submitted and then accepted as a Jupyter Enhancement Proposal (JEP) as part of the next version (v7): https://jupyter.org/enhancement-proposals/79-notebook-v7/notebook-v7.html
There is also a plan to move forward the current version (v6): https://github.com/jupyter/notebook-team-compass/issues/5#issuecomment-1085254000
#### Notebook v7
@ -31,6 +33,8 @@ To learn more about Notebook v7: https://jupyter.org/enhancement-proposals/79-no
Maintainance and security-related issues are now being addressed in the [`6.4.x`](https://github.com/jupyter/notebook/tree/6.4.x) branch.
A [`6.5.x`](https://github.com/jupyter/notebook/tree/6.5.x) branch will be soon created and will depend on [`nbclassic`](https://github.com/jupyter/nbclassic) for the HTML/JavaScript/CSS assets.
New features and continuous improvement is now focused on Notebook v7 (see section above).
If you have an open pull request with a new feature or if you were planning to open one, we encourage switching over to the Jupyter Server and JupyterLab architecture, and distribute it as a server extension and / or JupyterLab prebuilt extension. That way your new feature will also be compatible with the new Notebook v7.