JupyterLab 3.3 Release

[echarles]

Hi, I am opening this to discuss and gather inputs on a potential 3.3. release from the current 3.2 branch before the 4.0 release. We have a few ongoing PR that, if merged, would deserve a release before the 4.0 release.

The idea would be to get a 3.3. release in January 2022. Of course, if the 4.0 release is achievable by that time, we could skip that intermediary step.

List of pending PR to consider for 3.3 - Please edit this comment to add yours.

• Pause on exception #11752
• ☑️ Toggle side-by-side rendering for current notebook #11608
  Backport/3.2.x/11608 Toggle side-by-side rendering for current notebook #11718
  Backport on 3.3.x: Toggle side-by-side rendering for current notebook (#11793) #11794
  • Check if PR for resizing is already backported in 3.x
• Show the kernel sources as a debugger tab and allow the user to break in kernel sources #11566
  Backport PR #11566 on branch 3.3.x (Show the kernel sources as a debugger tab and allow the user to break in kernel sources) #11954
  Backport PR #12030 on branch 3.3.x (Debounce kernel sources filter) #12068
• Simple mode by default #11735.
  Backport PR #11881 on branch 3.3.x (Add startMode setting to define the startup mode) #11909
• ☑️ Add setting for the cell margin in side-by-side layout mode #11719
  Backport PR #11880 on branch 3.3.x (Add side-by-side margin override in the notebookConfig) #11948
• ☑️ Autosaving documents stacks duplicates file changed dialogs #11700
  Backport PR #11883 on branch 3.3.x (ensure a single modal is opened in case of time conflict savings) #11929
• Autocomplete broken for console #11710
  Backport PR #11949 on branch 3.3.x (Fix autocomplete in console) #11956
• ☑️ Drop testing Python 3.6, test on Python 3.10 #11646
  Backport PR #11646 on branch 3.3.x (Drop testing Python 3.6, test on Python 3.10) #11867
• ☑️ Drop support for Python 3.6 #11740
  Backport PR #11740 on branch 3.3.x (Drop support for Python 3.6) #11866
• ☑️ Add debugger variable renderer based on mime type #10299
  Backport PR #11171 on branch 3.3.x (Update variable renderer panels) #11874
• ☑️ Update variable renderer panels #11171
  Backport PR #11171 on branch 3.3.x (Update variable renderer panels) #11874
• ☑️ Add closeOnExit terminal option #11637
  Backport PR #11637 on branch 3.3.x (Add closeOnExit terminal option) #11868
• Add settings UI #11079
  • When backported rename the menu entry to keep the same Advanced Settings Editor
  • Check that the shortcut is maintained when backported
• ☑️ Allow extensions and users to customize easily toolbar items. #10469
  Backport PR #10469 on branch 3.3.x (Allow extensions and users to customize easily toolbar items.) #11873
• ☑️ List workspaces #11730
  Backport PR #11730 on branch 3.3.x (List workspaces) #11869
• ☑️ Add a command to open a file from a URL #11387
  Backport PR #11387 on branch 3.3.x (Add a command to open a file from a URL) #11870
• Terminal is blank when re-opening terminal tab (no scrollback is available) #10633
  • Pinging on the issue to figure out if someone plans to push a fix
• Allow to link factory to file type when adding it #11540
  Backport PR #11540 on branch 3.3.x (Allow to link factory to file type when adding it) #11940
• Backport PR #10730 on branch 3.3.x (Add execution progress indicator) #11941
• Support dynamic toolbar definition #11963

---

Edited to gather all suggestions
Edited with ☑️ to highlight backported PR to 3.3.x has been created

[krassowski]

I would propose:

• Add debugger variable renderer based on mime type #10299
• Update variable renderer panels #11171

[fcollonval]

@echarles in this week meeting, it was decided to carry out a 3.3 release in January (RC0 on 3rd week). We will review which features to bring in on January 12th meeting.

I propose:

• Add settings UI #11079
• Allow extensions and users to customize easily toolbar items. #10469

[ajbozarth]

I'll need to comb through the issues in more detail later, but off the cuff I know the small fix in #11540 is something Elyra would love to see in 3.3

[fcollonval]

• List workspaces #11730

[ohrely]

Could #11387 be included?

[zer0-memory]

I propose #10633

[fcollonval]

I propose #10633

@zer0-memory thanks for the suggestion. Due to our limited bandwidth, only features that are part of master will be added to JLab 3.3. So if you can help with fixing the mentioned issue, it will be great.

[jtpio]

Posting here some thoughts on how the JS packages should be versioned for 3.3.

Currently the packages are at the 3.2.x version on the 3.3.x branch:

If we want to go through the usual alpha -> beta -> rc -> final cycle, the versions will then be bumped to 3.3.0-alpha.x when we start releasing 3.3.0ax.

However these versions have already been used on master during the 4.0.0ax release series. For example:

https://github.com/jupyterlab/jupyterlab/blob/d1244eaa11eada494d98826e16ca42b31b9476f5/packages/application/package.json

And published to npm: https://www.npmjs.com/package/@jupyterlab/application/v/3.3.0-alpha.1

Something to keep in mind when we start making the 3.3 pre-releases. We might have to manually bump the versions first.

[jtpio]

Something to keep in mind when we start making the 3.3 pre-releases. We might have to manually bump the versions first.

Probably the simplest would then be to manually bump the JS packages to 3.3.0-alpha.16 on the 3.3.x branch. So we are still on alpha. This should help fix CI issues when backporting to that branch, as noticed in #11804.

[blink1073]

Any objections to backporting #11358 to 3.3.x? I can help @Zsailer with the backport if manual changes are required.

[jtpio]

FYI the first 3.3 prerelease is out: https://pypi.org/project/jupyterlab/3.3.0a1/

[jtpio]

3.3.0a2 is out: https://github.com/jupyterlab/jupyterlab/releases/tag/v3.3.0a2

[krassowski]

This one is a common ask:

• Switching tabs breaks the kernel status indicator #11903 (comment)

[trungleduc]

@krassowski I'm working on it #11941

[echarles]

We have said during our last dev meeting yesterday jupyterlab/frontends-team-compass#135 (comment) that we would release a new alpha next week.

Looking at all the PR merged since the last alpha release, I step-in to already make a new alpha release this week. Base on the status of the merged PR and the remaining ones, we can always make a new alpha release next week.

I hope this will work for everyone and that it will help to speed up the process for 3.3 final.

[fcollonval]

Major features are now merged in 3.3.x. Remaining PRs are listed in the 3.3.x milestone

[fcollonval]

@jtpio @echarles I saw in the latest changelog that @jupyterlab/ui-components has a different version (it is alpha.17 when all others are alpha.18). Should that be fixed or it does not matter?

[jtpio]

@fcollonval I think this is expected and related to the 3.3.0-alpha.x versioning that was on master (targeting 4.0) for a while (#11643 (comment))

This was noticed in #11810.

When we bump to 3.3.0b0 these numbers should normally be realigned.

[echarles]

Yes, I asked my self similar question in former releases. The different jupyterlab packages are bumped, but not enforced to be the same. I guess that is no change is seen, there is no bump. So a 3.3.0-alpha.x release will be composed of various npm packages version number. The pypi version has however to be aligned

Then bumping from eg alpha to beta will reset all that.

[echarles]

@jtpio we have further discussed the release plan at yesterday developer meeting and the consensus was to keep the final release date by end of February. This would imply a Beta release this week. I can handle that today if OK for you.

[jtpio]

Right we should be good for the beta now that most of the features have been backported. The remaining 3.3.x PRs are for fixing issues and they can be addressed during the beta cycle.

[fcollonval]

JupyterLab release 3.3.0 will be done on March 2nd at 4pm CET (7am PT). You can join the release on Zoom.

[jtpio]

JupyterLab 3.3.0 is out 🎉

• Release notes: https://github.com/jupyterlab/jupyterlab/releases/tag/v3.3.0
• Install with: pip install jupyterlab==3.3.0
• Some bug fixes are on the way and we will be releasing 3.3.x

Let us know if you find any issue. Thanks all!