Skip to content

Use semantic import versioning for published staging repos #72638

Closed
@nikhita

Description

Published staging repos like kubernetes/api, etc have tags like kubernetes-1.13.1 which correspond to the v1.13.1 tag in kubernetes/kubernetes. Due to the kubernetes- prefix, tools like dep don't pick up the new version.

We could start using semantic versioning for tags in published repos as well. One way to do that (as pointed by @sttts on slack) is to have the tags as 13.0.1. This is also a faithful representation of our compatibility guarantees.

This would require a change to the publishing-bot.

/sig api-machinery
/sig release
/area release-infra
/cc @sttts @pohly @lavalamp @deads2k @liggitt

Metadata

Assignees

No one assigned

    Labels

    area/code-organizationIssues or PRs related to kubernetes code organizationarea/release-engIssues or PRs related to the Release Engineering subprojectkind/featureCategorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.sig/releaseCategorizes an issue or PR as relevant to SIG Release.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions