3.1 Release Plan

[jasongrout]

We are currently in 3.1 beta phase.

We are planning on releasing the first release candidate, 3.1rc0, on July 12, 2021, with a final release to follow soon after. All known PRs and issues affecting JupyterLab code should be resolved by July 12 or bumped to the 4.0 milestone.

Update: we made the first release candidate, 3.1.0rc1 on July 13, 2021. Notionally the final release will be on July 27, 2021. All enhancements that were still on the 3.1 milestone have been moved to 4.0 and we created a 3.1.x branch, so master is now tracking 4.0.

[meeseeksmachine]

This issue has been mentioned on Jupyter Community Forum. There might be relevant details there:

https://discourse.jupyter.org/t/keyboard-shortcuts-with-overrides-json/5751/5

[blink1073]

I am planning to release the RC at 4pm ET today. At that point any in-progress enhancements will have to move to the 4.0 milestone. We can still work on bugs during the RC phase.

[blink1073]

I'm working on another beta release using Jupyter Releaser now that #10606 is merged. Ideally we will use releaser for the RC release today as well.

[echarles]

Great!. We have a few open PRs that deserve a bit more love and that would perfectly find their place in an upcoming 3.2 release if this is possible. I propose to add this topic at the agenda for our dev meeting.

[jasongrout]

FYI, I'm working on helping the autoclose brackets PR at #9488 get over the finish line.

[jasongrout]

FYI, I'm working on helping the autoclose brackets PR at #9488 get over the finish line.

I think #9488 is ready. It would be good if someone reviewed my last changes (or gave a sanity check about the final state of the PR) - the merge was a bit problematic since key relevant parts of master had changed since the PR was opened.

[blink1073]

We're running over time a bit to get #10545, #10609, and #9488 into the release

[blink1073]

We're going to cut the RC0 release first thing in the morning (ET) tomorrow to pick up #9488 and #10518

[bollwyvl]

Thanks for sticking with it, friends!

[blink1073]

Working on a beta 3 release, should finish in 10 minutes. If builds pass after that and local tests work, we'll merge #10612 and cut the RC with Jupyter Releaser automation. If not, we'll pull the beta 3 release and make a manual RC with #10612

[blink1073]

Okay, that build failed because of the previously failed beta 2. I'm going to take a gamble and make an RC using releaser, with the fallback plan of cutting a manual RC immediately after if needed.

[bollwyvl]

Seein' the .whl but no tar.gz:

https://pypi.org/project/jupyterlab/3.1.0rc0/#files

[bollwyvl]

Seeing it now, will start conda-forge

[blink1073]

RC 0 is broken, pressing with an RC1 manually

[blink1073]

RC1 is up

[bollwyvl]

conda-forge/jupyterlab-feedstock#282

[blink1073]

I created the 3.1.x branch. master is now targeting 4.0

[jasongrout]

What needs to happen during the RC phase?

• There are a few open issues that need to be investigated, and of course testing may turn up more.
• Time for external extensions to check compatibility (but likely won't need to be upgraded, since this is a minor release)
• Changelog to (probably?) edit
• Possibly a blog post to write

Anything else? Steve, did you want to get automated releases to work before the final 3.1?

Do we have a rough idea of how long we'll be in RC phase before a final release? 2-3 weeks, with a release by mid-August?

[blink1073]

I had updated the top level issue text this morning with answers to some of those questions.

[blink1073]

We ran into a problem with the automated release, should be fixed by #10621.

[blink1073]

I plan to make the release at 3 ET on Tuesday (27 July) unless there are any objections.

[blink1073]

Release is complete: https://github.com/jupyterlab/jupyterlab/releases/tag/v3.1.0