kubernetes/system-validators

decide on versioning and branching in this repo

neolit123 opened this issue · 3 comments

neolit123 commented

versioning in this repo is tricky and we need to make sure we introduce the proper tags and branches when we want to use a new version in k/k.

here are some ideas:

  • keep this repo bound to SEMVER
  • branch on MINOR versions, but don't break the "API" (not that it has much of that).
  • on breaking changes in the public functions, introduce a new MAJOR!
  • if introducing a new MINOR version of Docker for either of the OSes, bump the MINOR version from now on.
  • if adding validation for a Docker PATCH level bump, bump the PATCH level of the latest MINOR too.
  • try not to backport Docker bumps to older branches.

comments?

cc @rosti
/assign @yastij @neolit123

/kind design
/priority important-longterm

fejta-bot commented

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

neolit123 commented

i see no objections.
/close

k8s-ci-robot commented

@neolit123: Closing this issue.

In response to this:

i see no objections.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.