Skip to content

Add note to RELEASE_GUIDE.md on what to do when releases do not build as expected #4141

@JordanMartinez

Description

@JordanMartinez

See this comment. In short, update RELEASE_GUIDE.md to state that any releases (e.g. v0.14.3) that don't go as planned should not be removed. Rather, we should make a new release, update the release notes for that one to say that it's not a real release and refer people to the newer release (e.g. a v0.14.4 release had we followed these guidelines when making the v0.14.3 release).

Metadata

Metadata

Assignees

No one assigned

    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