Skip to content

Issue to trigger new releases #162

@ablaom

Description

@ablaom

Procedure for new releases:

  • merge new contributions onto dev (the base branch for PR's, by default)
  • bump version on dev
  • make a new PR dev -> master with the title like "For a 0.2.5 release" with list of PR's since last release, and merge if passing
  • make a new comment below to trigger a PR to General (see examples below) including release notes if appropriate (always the case if there are breaking changes). Again, see examples below. Alternatively, release notes can be edited after TagBot does it's thing.

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