Jupyterlab

Apr 04, 2017

Mainly backend-focused release with compatibility with Phosphor 1.0 and
a big refactor of session handling (the ClientSession class) that
provides a simpler object for classes like notebooks, consoles,
inspectors, etc. to use to communicate with the API. Also includes
improvements to the development workflow of JupyterLab itself after the
big split.

<https://github.com/jupyterlab/jupyterlab/pull/1984>
<https://github.com/jupyterlab/jupyterlab/pull/1927>

Mar 21, 2017

- Split the repository into multiple packages that are managed using
the lerna build tool.
<https://github.com/jupyterlab/jupyterlab/issues/1773>
- Added restoration of main area layout on refresh.
<https://github.com/jupyterlab/jupyterlab/pull/1880>
- Numerous bug fixes and style updates.

Mar 01, 2017

- Upgrade to new `phosphor` packages * brings a new Command Palette
interaction that should be more intuitive, and restores the ability
to drag to dock panel edges
<https://github.com/jupyterlab/jupyterlab/pull/1762>.
- Refactor of `RenderMime` and associated renders to use live models.
See <https://github.com/jupyterlab/jupyterlab/pull/1709> and
<https://github.com/jupyterlab/jupyterlab/issues/1763>.
- Improvements and bug fixes for the completer widget:
<https://github.com/jupyterlab/jupyterlab/pull/1778>
- Upgrade CodeMirror to 5.23:
<https://github.com/jupyterlab/jupyterlab/pull/1764>
- Numerous style updates and bug fixes.

Feb 09, 2017

- Adds a Cell Tools sidebar that allows you to edit notebook cell
metadata.
[1586](https://github.com/jupyterlab/jupyterlab/issues/1586).
- Adds keyboard shortcuts to switch between tabs (Cmd/Ctrl LeftArrow
and Cmd/Ctrl RightArrow).
[1647](https://github.com/jupyterlab/jupyterlab/issues/1647)
- Upgrades to xterm.js 2.3.
[1664](https://github.com/jupyterlab/jupyterlab/issues/1664)
- Fixes a bug in application config, but lab extensions will need to
be re-enabled.
[1607](https://github.com/jupyterlab/jupyterlab/issues/1607)
- Numerous other bug fixes and style improvements.


Making a JupyterLab release

This document guides a contributor through creating a release of JupyterLab.

The JupyterLab Release Process

JupyterLab follows [semver](https://semver.org/) for the versioning of the Python and JavaScript packages.

Release Timeline

Although the commitments listed below are "best effort", the JupyterLab team tries to follow a couple of guidelines:

- one major version per year, which usually includes API breaking changes
- several minor versions per year that include new features but no API breaking changes
- support and bug fixes on a couple of final releases (by backporting PRs and releasing from release branches)

Release Plans are tracked in dedicated issues, and are closed when the final release. See the following two issues as an example: