Skip to content

Define a proper release schedule/process for patches and minor releases #74

@joeribekker

Description

@joeribekker

Thema / Theme

API

Omschrijving / Description

Proposal from Anna:

Each refinement we can discuss the release for each component (so, monthly)

Topics to be discussed:

  • Are there any critical bugs / security issues that need to be fixed ASAP?
  • Are there any older dependencies that need to be replaced?

The upcoming releases will be in a new meta issue, and a linked issue for each component.

Release PRs need to be approved by Alex or Joeri (unless this proves difficult).

Proposal from Steven:

Addition to Anna: For minor/major releases, do the same as Anna proposes but less frequently.

Proposal from Conor:

Addition to Anna: Should allow for emergency releases (between refinements)

Proposal from Sonny:

Didn't see any benefit from periodic releases. Proposals above are fine.

Toegevoegde waarde / Added value

No response

Aanvullende opmerkingen / Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesttriageTriage means the team has not yet refined this issue.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions