diff options
| author | Marcin Owsiany <porridge@google.com> | 2017-10-18 07:46:38 +0200 |
|---|---|---|
| committer | Marcin Owsiany <porridge@google.com> | 2017-10-18 07:46:38 +0200 |
| commit | 34f2e3c77d6a09073e16b53d6b078462b5a2fc7a (patch) | |
| tree | 9afefa78f35442b0f425a080fc752516d6b52c0e | |
| parent | dd40878899fa5d9f72a9fd87f3b507d36820a672 (diff) | |
Change channel name for the rename.
| -rw-r--r-- | contributors/devel/scalability-good-practices.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/devel/scalability-good-practices.md b/contributors/devel/scalability-good-practices.md index 23ed7e2a..5769d248 100644 --- a/contributors/devel/scalability-good-practices.md +++ b/contributors/devel/scalability-good-practices.md @@ -160,7 +160,7 @@ When designing new features/thinking about refactoring you should: - when adding complex logic make sure that you don't add it on a critical path of any basic workflow ## Closing remarks -We know that thinking about performance impact of changes that all of us write is hard, this is exactly why we want you to help us cater for it, by always having problems that we mentioned here in the back of your mind. In return we'll answer all your question and doubts about possible impact of your changes if you post them either to #sig-scale Slack channel, or cc @kubernetes/sig-scalability-pr-reviews in your PR/proposal. +We know that thinking about performance impact of changes that all of us write is hard, this is exactly why we want you to help us cater for it, by always having problems that we mentioned here in the back of your mind. In return we'll answer all your question and doubts about possible impact of your changes if you post them either to #sig-scalability Slack channel, or cc @kubernetes/sig-scalability-pr-reviews in your PR/proposal. * * * |