New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: devel: Add some notes about OWNERS process #37640
docs: devel: Add some notes about OWNERS process #37640
Conversation
cc @apelisse cc @michelleN (since doc move is in progress) |
@@ -9,6 +9,8 @@ will serve as the approvers for code to be submitted to these parts of the repos | |||
are not necessarily expected to do the first code review for all commits to these areas, but they are | |||
required to approve changes before they can be merged. | |||
|
|||
**Note** The Kubernetes project has a hiatus on adding new approvers to OWNERS files. At this time we are [adding more reviewers](https://github.com/kubernetes/kubernetes/pulls?utf8=%E2%9C%93&q=is%3Apr%20%22Curating%20owners%3A%22%20) to take the load off of the current set of approvers and once we have had a chance to flush this out for a release we will begin adding new approvers once again. This is planned for the post Kubernetes 1.6.0 has been released |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hate nitpicking tiny PRs, but the last sentence here does not parse as English.
Document that we are currently holding off on adding new approvers until the reviewers process is in place. And set a target deadline.
All of the tracking is happening here kubernetes-retired/contrib#1389 point people at it.
@Thocking fixed.
…On Tue, Nov 29, 2016 at 1:05 PM Tim Hockin ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In docs/devel/owners.md
<#37640 (review)>
:
> @@ -9,6 +9,8 @@ will serve as the approvers for code to be submitted to these parts of the repos
are not necessarily expected to do the first code review for all commits to these areas, but they are
required to approve changes before they can be merged.
+**Note** The Kubernetes project has a hiatus on adding new approvers to OWNERS files. At this time we are [adding more reviewers](https://github.com/kubernetes/kubernetes/pulls?utf8=%E2%9C%93&q=is%3Apr%20%22Curating%20owners%3A%22%20) to take the load off of the current set of approvers and once we have had a chance to flush this out for a release we will begin adding new approvers once again. This is planned for the post Kubernetes 1.6.0 has been released
I hate nitpicking tiny PRs, but the last sentence here does not parse as
English.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#37640 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACDCEicqe94G1rAJD0sya9rceAbGweXks5rDJN7gaJpZM4K_UW->
.
|
lgtm |
/lgtm |
gah, the CLA label didn't get applied, I think. |
@foxish Does |
Yes it does. The submit queue knows to honor the human approved label.
…On Nov 29, 2016 5:58 PM, "Brian Grant" ***@***.***> wrote:
@foxish <https://github.com/foxish> Does cla: human-approved work for
CNCF CLA?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#37640 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA3U5352VviJvmZ4K_QLl5r6STEHThJHks5rDNhUgaJpZM4K_UW->
.
|
Can someone apply the label? CoreOS has a CLA for both Google and CNCF. |
Automatic merge from submit-queue |
@foxish ah, yes, you are right. |
Sorry! github's UI is too slow and clunky |
docs: devel: point people at place for OWNERS status
All of the tracking is happening here
kubernetes-retired/contrib#1389 point people at it.
docs: devel: describe the current state of adding approvers
Document that we are currently holding off on adding new approvers until
the reviewers process is in place. And set a target deadline.
cc @calebamiles @bgrant0607 @apelisse