📖 Versioning and Branching Strategy #216
Conversation
k8s-ci-robot
added
the
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DirectXMan12 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 |
k8s-ci-robot
added
approved
|
@droot @pwittrock PTAL and let me know what you think |
|
|
||
| ### Breaking Changes | ||
|
|
||
| Try to avoid breaking changes. They make life difficult for users, who |
There was a problem hiding this comment.
Can we provide a sed operation to automatically fix any breaking changes with defaults that maintain the old behavior or provide some new default?
There was a problem hiding this comment.
Probably want more intelligent than sed, but it should be possible to do so
droot
added
the
lgtm
This adds in documentation on versioning, branching, and maintenance. There's still a couple of places where we have to create scripts and fill in process, but this lays the initial groundwork.
DirectXMan12
force-pushed
the
docs/branching-strategy
branch
from
657d0aa to
64a9833
Compare
|
New changes are detected. LGTM label has been removed. |
k8s-ci-robot
removed
the
lgtm
DirectXMan12
changed the title
k8s-ci-robot
removed
the
do-not-merge/work-in-progress
|
|
||
| ### Mantainers | ||
|
|
||
| Don't be lazy, read the rest of this doc :-) |
| ### Contributors | ||
|
|
||
| - All code PR must be labeled with :bug: (patch fixes), :sparkles: | ||
| (backwards-compatible features), or :warning: (breaking changes) |
There was a problem hiding this comment.
Github PR template can help us here.
droot
added
the
lgtm
…ng-strategy 📖 Versioning and Branching Strategy
This is mostly a proposal at this point. I've started to outline the branch strategy we've loosely discussed in the past, with some motivations and discussion of alternatives.