Final v3.0.0 release

[davidbrochart]

It seems to me that we could release jupyter-collaboration v3.0.0. I installed v3.0.0b3 and it works fine with JupyterLab v4.2.5. Or should we make another pre-release that includes the timeline?

[davidbrochart]

What do you think about including #353?

[jtpio]

Or should we make another pre-release that includes the timeline?

Is the timeline opt-in? Or can it be collapsed? Thinking it might take quite some space in the status bar, according to the screencast in the blog post: https://blog.jupyter.org/exploring-a-documents-timeline-in-jupyterlab-6084f96db263

If so, it could be useful to mention it in the docs: https://jupyterlab-realtime-collaboration.readthedocs.io/en/latest/

[davidbrochart]

Is the timeline opt-in?

It's not opt-in, but if you don't use it then no slider is shown, only this icon:

[krassowski]

I think we should sync it with JupyterLab 4.3.0 final. I think we do not have to wait for #345 but it would be lovely to include it if we can.

[davidbrochart]

I think we should sync it with JupyterLab 4.3.0 final.

When do you see this happening?

[krassowski]

One week after RC gets published assuming no new blockers

[davidbrochart]

I just released jupyter-collaboration v3.0.0b4.

[davidbrochart]

I think we should sync it with JupyterLab 4.3.0 final.

But why does it need to be synced, since it works with JupyterLab 4.2.5?

[krassowski]

Ah, the dependency is the other way round. JupyterLab 4.3 requires the new collaboration packages to have lifted ydoc version pin, right? In that case I guess it does not need to wait :)

[davidbrochart]

JupyterLab 4.3 requires the new collaboration packages to have lifted ydoc version pin, right?

Yes. I just tried jupyter-collaboration v3.0.0b4 with JupyterCAD, everything seems to work fine.
I'd like to have #353 in before the final release, it will allow to swap jupyter-collaboration with jupyter-shared-drive (or any other collaboration system that implements the ICollaborativeDrive), and have support for JupyterLite.

[krassowski]

So we are good to release final, right?

[davidbrochart]

There is still #353 that would be good to get in before v3. If it's merged after v3 that would be another breaking change. I'll rebase it.

[davidbrochart]

I just release v3.0.0beta8 which has #353, everything seems to work fine.
I guess we are good to release v3.0.0 final?

[davidbrochart]

One thing I noticed is that when creating a new notebook, no empty cell is created, even though jupyterlab/jupyterlab#16732 was not merged yet. It might be because of jupyter-server/jupyter_ydoc#266, but I thought this was not enough and the frontend added an empty cell if there was no cell.

[davidbrochart]

I confirm it's caused by jupyter-server/jupyter_ydoc#266.

[davidbrochart]

I think we should merge jupyterlab/jupyterlab#16732 and have jupyter-server/jupyter_ydoc#266 enabled when allowEmptyNotebook is true.

[davidbrochart]

I'm planning to release v3 soon, if there are no objections.

[davidbrochart]

I reverted jupyter-server/jupyter_ydoc#266 in jupyter-server/jupyter_ydoc#280.
I don't see any blocker to release jupyter-collaboration v3.0.0 final. I'll do it today or tomorrow, please let me know if you have any objection.

[davidbrochart]

Hmm prep_release failed. Could it be due to #343 @brichet?

[jtpio]

Did you specify the correct version spec? https://github.com/jupyterlab/jupyter-collaboration/blob/main/RELEASE.md#version-specification

[davidbrochart]

Oh I was not aware of this, I just specified 3.0.0 and thought it would work.
It seems I could use release but it means we need to make an rc before?

[jtpio]

yeah it's also a good practice to make an rc first.

[jtpio]

But then it can be weird to do the final release right after. Maybe do it on Monday to give the rc a few days? (or at least the weekend).

When you do the final release, check this box so the changelog is correctly populated:

[davidbrochart]

OK, let's release v3.0.0 final next week. I just released v3.0.0rc0.

[davidbrochart]

Since #379 seems to target v3.1.0, should we release v3.0.0 now?

[jtpio]

Similar to this JupyterLab 4.3.0 (blocker) issue: jupyterlab/jupyterlab#16649

Are we fine to depend on an alpha release of @jupyter/ydoc?

jupyter-collaboration/packages/collaborative-drive/package.json

Line 40 in b64b54b

"@jupyter/ydoc": "^2.0.0 || ^3.0.0-a3",

[davidbrochart]

We could release @jupyter/ydoc v3.0.0 before, and update the dependency here?

[jtpio]

Yes, but from the discussion in jupyter-server/jupyter_ydoc#281, there seems to be one more issue to be fixed in jupyter_ydoc first before: jupyter-server/jupyter_ydoc#269

[davidbrochart]

Ah yes I forgot.

[davidbrochart]

I just bumped jupyter-ydoc v3.0.0, and I am going to release jupyter-collaboration v3.0.0 final.

[davidbrochart]

Done: https://github.com/jupyterlab/jupyter-collaboration/releases/tag/v3.0.0.