Skip to content

Describe provider versioning changes with semver #11425

@potiuk

Description

@potiuk

We agreed that provider package versioning needs to be done with semver. We need to work out the way on how this automated versioning would work from those perspectives:

  • contributor
  • maintainer
  • release manager

Short documentation about this would be great, before we implement that, so that we know what could be automated and what should be manual work.

We need to agree on:

  • how to increment the values when we release each package
  • based on what criteria
  • how the contributors should mark the PRs as bugfixes/features (needed for automation)
  • how maintainers should verify it
  • whether release manager needs to do some verification
  • decide how we release sources - all together or as separate set of sources per package : Separate.
  • manage cross provider dependencies
  • tagging mechanism: separate tag per providers
  • how we approach relating patchlevels for minor versions and minor versions for major ones (say we have 2.0.0 and 1.1.0 of providers out there - how do we approach relating 1.1.1 with bugfixes).

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions