[WIP] makefile wrapping concept #621
Conversation
The order of operations in the release workflow is a mix of complicated, error-prone command invocations, and manual synchronization check points. A summary of these is needed to make the required actions more clear. Also adds a table of contents as intradoc links makes eaiser navigating to the appropriate info a different points in a process that spans days or even weeks. Signed-off-by: Tim Pepper <tpepper@vmware.com>
For a concrete discussion on tools improvement, I want to show what I'm imagining it might look like to establish a wrapping of the detailed commands which do build and publish. My goal is to allow parallel back end implementations and proof-of-concept comparisons. If the top level flow is abstracted and callable by automation, without those tools getting coupled to the internal implementation, we are in a more flexible and testable place and enable more to be done through automation.
tpepper
added
the
area/release-eng
tpepper
requested review from
akutz,
justaugustus,
hoegaarden,
codenrhoden,
aleksandra-malinowska and
Bubblemelon
k8s-ci-robot
added
do-not-merge/work-in-progress
|
/hold here for discussion |
k8s-ci-robot
added
do-not-merge/hold
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tpepper 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
the
approved
k8s-ci-robot
added
the
needs-rebase
|
@tpepper: PR needs rebase. 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. |
|
/milestone v1.16 |
k8s-ci-robot
added
the
priority/important-longterm
k8s-ci-robot
added
kind/documentation
|
/close |
|
@justaugustus: Closed this PR. In response to this:
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. |
The commit looks fugly, but basically is adding a third column to the table introduced in #620
For a concrete discussion on tools improvement, I want to show what I'm imagining it might look like to establish a wrapping of the detailed commands which do build and publish.
My goal is to allow parallel back end implementations and proof-of-concept comparisons. If the top level flow is abstracted and callable by automation, without those tools getting coupled to the internal implementation, we are in a more flexible and testable place and enable more to be done through automation.