Skip to content

Treat v-prefixed branch as release for release-branch-semver? #571

@QuLogic

Description

@QuLogic

The release-branch-semver scheme appears to match what we do in Matplotlib pretty closely. Since we make tags like v1,2,3, our branches are named like v1.2.x. This unfortunately is not treated as a release branch because of the v prefix in the branch name, even though the v prefix is dropped from the tag.

Now, we've never made a release branch with setuptools-scm, so this is something we could change, but it'd require updating a bunch like docs, CI, etc.

Does this make sense to handle this prefixing in the release-branch-semver?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions