jupyter-server/team-compass

Jupyter Server 2.0

Zsailer opened this issue · 3 comments

Zsailer commented

It looks like the new Identity API might need to introduce some backwards incompatible changes, warranting a new major release of Jupyter Server (i.e. 2.0).

I am opening this issue for two reasons:

  1. make everyone aware of this change to avoid inadvertently publishing this feature in a 1.x release.
  2. discuss a strategy for branching and releasing going forward.

I'll do some poking around other Jupyter subprojects to see how these things are managed elsewhere. In the meantime, if anyone wants to provide their own insights, feel free to comment below.

Thanks!

blink1073 commented

I created a 2.0 milestone and also added jupyter-server/jupyter_server#651

  • ❤️1
echarles commented

Replying here on comment from @fcollonval #15 (comment)

Is needed for JupyterLab 4.0, i.e. before June? No.

I disagree on that point. Identity is needed for RTC and we certainly hope to get a first decent RTC experience in 4.0.

I am +0.5 :) on @fcollonval comment. There are other features needed to bring that decent RTC experience in 4.0. :)

As the identity API is a needed building block for RTC, I agree jlab-4 depending on jserver-2 would be a good fit.

  • 👍1
vidartf commented

We're well on the way to a 2.0 release, so I think we have resolved the points brought up in the issue.