Skip to content

Cutting pre-release policy #459

Description

@dlqqq

cc @jtpio @brichet

Hey folks, I'm going to cut a v0.23.0a0 pre-release to help test changes to help verify JupyterLab v4.6 support. (mainly this: jupyter-ai-contrib/jupyter-server-documents#264)

I'm just going to do it now since I'm 99% confident that this is safe (as it won't be installed by default). Wanted to open an issue to confirm this though: are we OK with each other cutting pre-releases whenever?

To me, cutting pre-releases seems always safe and it makes things way easier to test, so I'd be happy if we each can cut pre-releases whenever we want to test things with another repo.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions