Release 6.1.0

[kevin-bates]

There have been some pull requests merged (and others waiting) that probably warrant more than a patch release, so I'd like to start the process of putting things together for a Notebook 6.1.0 release. Preferably, this would be based on master.

Here are the commits since 6.0.3, most of which came with #4479 - which is a primary reason for introducing a minor release.

Other PRs I think we should include - although I don't necessarily expect all these to make the release...

• Add ability to cull terminals and track last activity Add ability to cull terminals and track last activity #5372 (Zach, reviewed)
• Add UNIX socket support to notebook server. Add UNIX socket support to notebook server. #4835 (Steve)
• [WIP] Make the last modified date consider files in subdirectory [WIP] Make the last modified date consider files in subdirectory #5336 (front-end review required) (Zach, won't be ready in the near future).
• Added nl language Added nl language #5354
• tree added download multiple files tree added download multiple files #5351 (front-end review required) (Zach)
• Readme viewer Readme viewer #5299 (front-end review required) (Zach, discuss at next meeting)
• Make a notebook writable after successful save-as Make a notebook writable after successful save-as #5296 (front-end review required) (Darian)
• implement natural sorting fixes 5230 implement natural sorting fixes #5230 #5259 (front-end review required) (Darian: changes requested) (deferred to next release)
• Add env variable support for port options Add env variable support for port options #5221 (Steve)
• Update CodeMirror dependency Update CodeMirror dependency #5198 (front-end review required) (Steve)
• Toolbar buttons tooltip: show help instead of label Toolbar buttons tooltip: show help instead of label #5107 (front-end review required) (Darian)
• kill notebook its self when server cull idle kernel kill notebook its self when server cull idle kernel (new fix) #5593 (front-end review required) (Zach—approved, waiting for reply since tests are failing)
• Adjust buffer replay logic for restarts w/ new ports Adjust buffer replay logic for restarts w/ new ports #5450 (deferred to jupyter_server)
• Added functionality to allow filter kernels by Jupyter Enterprise Gat… Added functionality to allow filter kernels by Jupyter Enterprise Gat… #5484 (Kevin)
• Bump minimum version of jQuery to 3.5.0 Bump minimum version of jQuery to 3.5.0 #5491 (Kevin)
• (Issue) Backspace doesn't delete empty line Backspace doesn't delete empty line #5502
• Update changelog (Kevin) - (latest updates)
• Improve login shell heuristics Improve login shell heuristics #5588
• Add support for JUPYTER_TOKEN_FILE Added support for JUPYTER_TOKEN_FILE #5587 (Kevin)
• Russian I18N support russian i18n - 100% #5571 (Kevin)
• Paste two images Fixes 3182 #5598 (front-end review required) (Steve)
• Add a metadata tag to override notebook direction (ltr/rtl) Add a metadata tag to override notebook direction (ltr/rtl) #5052 (Steve)
• Add keyboard shortcuts to menu dropdowns Add keyboard shortcuts to menu dropdowns #5525 (Steve)
• Resolve CodeMirror version issue (5.53.2 vs. 5.55+) Code not centered properly in cell #5629 (Steve,Kevin)

If there are other issues and/or pull requests you'd like to see in a 6.1.0 release, please add comments and I'll amend this text - or feel free to amend this yourself (if privs allow).

[willingc]

@blink1073 @kevin-bates Would it be possible to release a 6.0.4 with minimally the fix for #4835 which prevents installing in a Python 3 virtual environment? Installing requests-unixsocket would not resolve the install failure. Pulling master and building from HEAD worked.

Alternatively, 6.1 would be great too. 😄

[kevin-bates]

Hi @willingc - thanks for the heads up.

I'm a little confused in trying to understand your comment from an urgency perspective. Neither #4835 nor the fix I believe you're referring to (#5451) have been released - both in master waiting for their "carrier". So was your py3 installation issue the result of cherry-picking #4853 (having not also taken #5451)?

Our intention is to build 6.1 from master but if there's more at play here I suppose we could look into an interim patch release. Although, having never built a notebook release, I should defer to Steve on that.

I was going to suggest at least one rc release (for 6.1) so we can discover, and workout, any kinks as well.

[kevin-bates]

Release 6.1.0rc1 has been pushed to PyPI. Does conda-forge handle pre-releases? If so, I'd prefer to wait to announce the RC.

I was going to post in the google groups, gitter, and discourse forums. Are there other locations?

[blink1073]

Thanks!

Pre-releases on conda are possible: I added an rc branch to the feedstock.
Here is an example rc PR from JupyterLab: conda-forge/jupyterlab-feedstock#206
And the JuptyerLab branch: https://github.com/conda-forge/jupyterlab-feedstock/tree/rc

I think those ANN locations sound good.

[kevin-bates]

Thanks Steve! I've submitted conda-forge/notebook-feedstock#68 targeting the rc branch and based on the jupyterlab example.

[kevin-bates]

@Zsailer, @blink1073, @afshin - could you please review the set of unmarked tasks above? I think we need to try to get 6.1 out soon (preferably next week) and I believe the unmarked items are ready (with the exception of #5259).

Also, Steve, I noticed you marked some of these with a 6.2 milestone and I suspect that was to prevent 'feature creep'. Just wondering your thoughts on including them in 6.1?

I'd like to go ahead and include the Russian I18N work since that's the kind of thing that shouldn't be too disruptive if there are issues that were not caught in review. Any objections?

[blink1073]

I just didn't want to step on your toes. I merged the ones that were waiting in the wings.

[Zsailer]

Thank you for championing this forward, @kevin-bates! I merged #5593.

I would think we should bump #5259 to 6.2, since there hasn't been activity on that PR in awhile.

I'd like to go ahead and include the Russian I18N work since that's the kind of thing that shouldn't be too disruptive if there are issues that were not caught in review. Any objections?

👍 I agree!

[afshin]

I agree with Zach. If they do not come back to update it, I can take a more serious look at that PR if we think it's important and we can put it in 6.2.

[kevin-bates]

Thank you for your timely responses and all your help! I'll finalize the changelog and let things sit for a day or so, then release 6.1.0 GA.

[kevin-bates]

Release 6.1.0rc1 has been pushed to PyPI. Does conda-forge handle pre-releases? If so, I'd prefer to wait to announce the RC.

I was going to post in the google groups, gitter, and discourse forums. Are there other locations?

[blink1073]

Thanks!

Pre-releases on conda are possible: I added an rc branch to the feedstock.
Here is an example rc PR from JupyterLab: conda-forge/jupyterlab-feedstock#206
And the JuptyerLab branch: https://github.com/conda-forge/jupyterlab-feedstock/tree/rc

I think those ANN locations sound good.

[kevin-bates]

Thanks Steve! I've submitted conda-forge/notebook-feedstock#68 targeting the rc branch and based on the jupyterlab example.

[kevin-bates]

@Zsailer, @blink1073, @afshin - could you please review the set of unmarked tasks above? I think we need to try to get 6.1 out soon (preferably next week) and I believe the unmarked items are ready (with the exception of #5259).

Also, Steve, I noticed you marked some of these with a 6.2 milestone and I suspect that was to prevent 'feature creep'. Just wondering your thoughts on including them in 6.1?

I'd like to go ahead and include the Russian I18N work since that's the kind of thing that shouldn't be too disruptive if there are issues that were not caught in review. Any objections?

[blink1073]

I just didn't want to step on your toes. I merged the ones that were waiting in the wings.

[Zsailer]

Thank you for championing this forward, @kevin-bates! I merged #5593.

I would think we should bump #5259 to 6.2, since there hasn't been activity on that PR in awhile.

I'd like to go ahead and include the Russian I18N work since that's the kind of thing that shouldn't be too disruptive if there are issues that were not caught in review. Any objections?

👍 I agree!

[afshin]

I agree with Zach. If they do not come back to update it, I can take a more serious look at that PR if we think it's important and we can put it in 6.2.

[kevin-bates]

Thank you for your timely responses and all your help! I'll finalize the changelog and let things sit for a day or so, then release 6.1.0 GA.

[kevin-bates]

6.1.0 is released - thank you all for your help with this!