-
Notifications
You must be signed in to change notification settings - Fork 1.6k
initial go modules draft #908
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
initial kep lgtm. thumbs up to merge and iterate from me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@liggitt Nicely written and the timing works well. Thanks for putting this together.
/hold Adding hold until an approver on the KEP pokes at it. |
LGTM, +1 to merge and iterate! |
/cc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is cool. lgtm
@smarterclayton @thockin can either of you approve this so we can merge? |
* uses latest commits of transitive non-module-based dependencies (likely to break, as today) | ||
* module-based consumers | ||
* reference published modules versions as a consistent `vX.y.z` version (e.g. `v15.0.0`) | ||
* import `k8s.io/apimachinery/v15/...` (have to rewrite kubernetes component imports on every major version bump) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Conversely, if we actually did the right thing (as defined by go) and kept the old versions functioning correctly (e.g. v14.x.y itself imports v15 and adapts), then this would only be necessary when people actually wanted the new interface.
...I'm not claiming the demand go makes is reasonable, but if old packages stop working or stop working with new packages, we are not doing it the way they intended.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not necessarily opposed to adopting semantic import versioning, but I see that as a discrete step, and one that should wait at least until we don't have to worry about GOPATH consumers as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree.
- "@mattfarina" | ||
approvers: | ||
- "@smarterclayton" | ||
- "@thockin" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm also willing to be on either of these lines
/approve For initial status. Agreed with Jordan’s assessment on semantic versioning being a discrete step and orthogonal to short term inprovements to tooling. |
unholding, will fold in updates for some comments in the next PR /hold cancel |
/lgtm (@mattfarina and @cblecker indicated their LGTM earlier plus mine as well) |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, liggitt, mattfarina, smarterclayton 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As part of this, perhaps we can also simplify some of the hack/* tools (e.g. get rid of run-in-gopath.sh) and maybe simplify the _output/... mess
I'd like to see those things get cleaned up, definitely, but we're sitting in between GOPATH and go modules at the moment. The output of this proposal produces a |
next PR updating this KEP is in #916 |
Initial go modules draft KEP.
/sig architecture testing release api-machinery
/cc @lavalamp @sttts