This is long overdue, but…
Announcing the first major release of the Jupyter Server project!
Two major things to be aware of:
- JupyterLab 3.0 will now depend on Jupyter Server, not Jupyter Notebook for its tornado webserver
-
jupyter_server(and other related server-side repos) is moving to its own Github org, jupyter-server.
TL;DR
Background
This project began as a fork of the Jupyter Notebook backend—the Tornado webserver, core services and APIs, REST endpoints—without the Notebook frontend.
There was an initial Jupyter Enhancement Proposal submitted 4 years ago. In May 2019, we had a Jupyter Community Workshop where we developed the roadmap to Jupyter Server 1.0. Now, we are pleased to announce the 1.0 release of Jupyter Server.
Impact
The upcoming release of JupyterLab 3.0 will use this new server in place of the classic Notebook server.
Other clients such as Voila have also been moving toward using the new Jupyter server.
Server extension authors are encouraged to make their server extensions compatible with both the classic Notebook and Jupyter Server. There is currently automatic shimming that handles most use cases, but further instructions are here for users and here for server extension developers.
New jupyter-server Github org
Given the momentum around Jupyter Server, the Jupyter Server Team is planning to start a new Github org and move the jupyter_server repo here. This new org will enable us to organize our work around Jupyter Server more effectively. We’ll create a team-compass page for meeting notes, public discussion, roadmaps, voting, etc. to make participation around Jupyter Server more open and transparent. This org will also provide a home for server-related extensions and experimental projects.
Currently, the Jupyter Server Team hosts weekly meetings. These meetings are open to anyone. We (try to) maintain notes from these meetings so anyone can follow along asynchronously. We hope to see you there!