Skip to content

Tracking issue for the next release #2107

@tisonkun

Description

@tisonkun

Hi all!

I'm starting this issue to track tasks for the next release.

I'd like to know:

  1. Are there any pending issues to be resolved before we cut the next release?

I'm seeing two candidates:

But we can first cut a release to denote the revival of this project and handle them in the next.

  1. How do we typically cut a release?

Now we're migrating the project manager to uv, perhaps we should verify the release process once again.

What do you think?

cc @micafer @Kami @PsiACE

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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