Skip to content

3.0 Release Plan #8038

@jasongrout

Description

@jasongrout

Timeline

We released JupyterLab 3.0 on 24 Dec 2020. The changelog is in the documentation.

Major features

We want major features in 3.0 to entice users to upgrade.

Some other possibilities included (deferred):

Known Breaking API Changes

  • The semantics of dynamic extensions will be different from regular extensions
  • Url semantics will change due to single document mode
  • Upgrade from TS 3.7 -> 3.9 affects typing APIs
  • Many APIs take an optional ITranslator object

Checklist

Beta

  • Update extension guide to use module federation
  • Update dependencies in various package.json files and refresh the yarn.lock to pull in latest versions

Release checklist

Now do the actual final release:

  • Run jlpm run bumpversion release to switch to final release

  • Push the commit and tags to master

  • Run npm run publish:all to publish the packages

  • Create a branch for the release and push to GitHub

  • Update the API docs

  • Set the default branch of the APOD repo.

  • Publish to conda-forge.

After a few days (to allow for possible patch releases), set up development for
the next release:

Metadata

Metadata

Assignees

No one assigned

    Labels

    status:resolved-lockedClosed inactive issues are locked after a while. Please open a new issue for related discussion.tag:DevOps

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions