diff options
| author | Tim Pepper <tpepper@vmware.com> | 2018-06-15 09:40:25 -0700 |
|---|---|---|
| committer | Tim Pepper <tpepper@vmware.com> | 2018-06-15 09:40:25 -0700 |
| commit | 2d8e8181fa7ceb9ea1825c013c903563b1020dff (patch) | |
| tree | 87757f69152422bf4a0912a4e49db2b84da0dc2b /github-management | |
| parent | a101484fbb1b8aeef307a148b58116f40f060d51 (diff) | |
contributors/devel: request better godep vendoring commit messages
On the release team I've seen a number of issues go by this year
where vendor code was updated and later implicated in issue triage
and bisection, but the original commits didn't sufficiently document
the change. Reverting the update then reintroduced a previously
fixed issue, which was insufficiently documented in the changelog. The
subsequent churn led to a lot of work by multiple people to resolve.
Terse godep vendor code update commit messages seem to be the norm and
we should aim higher.
Signed-off-by: Tim Pepper <tpepper@vmware.com>
Diffstat (limited to 'github-management')
0 files changed, 0 insertions, 0 deletions
