Skip to content

Release strategy #36

Closed
Closed
@jankapunkt

Description

@jankapunkt

How do we want to release a new version?

  • who should release? -> human vs GitHub Actions?
  • when to release?
  • how to prepare a release? -> one release branch with tags or one branch for each major version? like release-4.x, release-5.x
  • do we want additional tests that run in GitHub actions when merging to a release branch? GH Actions is so flexible I could even clone another repo and install the intended release package into it and run tests, so we can test adapter-compliance and even the example repo if we want. There are no limits :-)
  • who is responsible for release management and the deployment keys, npm repo etc.?
  • do we also want to release to GitHub packages as a redundancy factor?
  • what else....?
  • do we want to hold these information in a `MAINTAINERS.md? ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    discussion 🗨️Discussion about a particular topic.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions