community/contributors
Tim Pepper 2d8e8181fa 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>
2018-06-15 09:40:25 -07:00
..
design-proposals Update quota support for priority proposal according to the implementation 2018-06-15 08:46:42 -04:00
devel contributors/devel: request better godep vendoring commit messages 2018-06-15 09:40:25 -07:00
guide add a notice that the good first issue label is new and a WIP 2018-06-12 14:34:58 -04:00
new-contributor-playground Typo fix: excuted->executed 2018-05-16 23:19:57 +08:00