Skip to content

Issues while releasing patch release that isn't the latest release #415

@ysbaddaden

Description

@ysbaddaden

Here are my notes regarding the release of 1.19.2 that happened after the release of 1.20.0, so we didn't push the latest release:

  • Docs: the make command in the steps documents to run both the publish_docs and release_latest_docs targets but that would replace the default redirections! Only run make -C docs publish_docs.

  • Docker: the script to push the tags replaces the latest, major and minor tags! Edit the script to only replace the minor tag.

  • Snapcraft: building 1.19.2 pushed the build as latest/edge, until the nighly build of 1.21.0-dev replaced it. No idea how to prevent that.

  • Website: the website considers the release as being the latest one.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions