Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automated cherry pick of #8373: Prefix git tags with v #8421

Conversation

johngmyers
Copy link
Member

Cherry pick of #8373 on release-1.16.

#8373: Prefix git tags with v

For details on the cherry pick process, see the cherry pick requests page.

Go modules require the v prefix [0], and k/k also tags with the v prefix [1]

We have some inconsistent tags already, for 1.11.0 we have tags of both `1.11.0` and `v1.11.0` which is the most recent tag with the prefix.
This is also why 1.11.0 is the default version imported by `go get`:

```
go get -v k8s.io/kops
go: downloading k8s.io/kops v1.11.0
```

and the latest version in `go list`:

```
go list -m -versions k8s.io/kops
k8s.io/kops v1.4.0-alpha.1 v1.4.0 v1.4.1 v1.4.2 v1.4.3 v1.4.4 v1.10.0 v1.11.0
```

I'm proposing we switch to only tagging with the v prefix. I'm only updating the actual git tag and not the entire version string used throughout kops due to its larger impact:

* Output by `kops version`
* Public URLs for kops assets
* Protokube tag

I'm hoping this is the least invasive way we can make this change.
If we think advanced notice is required, we could tag with both formats for a number of releases before tagging only with the v prefix.

[0] https://github.com/golang/go/wiki/Modules#modules
[1] https://github.com/kubernetes/kubernetes/releases/tag/v1.17.0
@k8s-ci-robot k8s-ci-robot added this to the v1.16 milestone Jan 27, 2020
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 27, 2020
@johngmyers
Copy link
Member Author

/retest

1 similar comment
@hakman
Copy link
Member

hakman commented Jan 27, 2020

/retest

@rdrgmnzs
Copy link
Contributor

/test pull-kops-e2e-kubernetes-aws-1-16

@rifelpet
Copy link
Member

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 28, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johngmyers, rifelpet

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 28, 2020
@k8s-ci-robot k8s-ci-robot merged commit 8eae343 into kubernetes:release-1.16 Jan 28, 2020
@johngmyers johngmyers deleted the automated-cherry-pick-of-#8373-upstream-release-1.16 branch January 28, 2020 05:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants