Skip to content

Rename next_api_changes to api_changes_3.x (whatever number makes sense) #16588

Closed
@anntzer

Description

@anntzer

Putting an actual version number on the next_api_changes directory may help avoiding notes going to the wrong file during long RC periods where it's not so obvious whether next_api_changes refers to the currently rc'd release, or the next one. See e.g. #16457 (comment).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions