diff options
| -rw-r--r-- | pr_workflow.dia | bin | 0 -> 1987 bytes | |||
| -rw-r--r-- | pr_workflow.png | bin | 0 -> 27835 bytes | |||
| -rw-r--r-- | pull-requests.md | 7 |
3 files changed, 5 insertions, 2 deletions
diff --git a/pr_workflow.dia b/pr_workflow.dia Binary files differnew file mode 100644 index 00000000..d520c21d --- /dev/null +++ b/pr_workflow.dia diff --git a/pr_workflow.png b/pr_workflow.png Binary files differnew file mode 100644 index 00000000..dc95a366 --- /dev/null +++ b/pr_workflow.png diff --git a/pull-requests.md b/pull-requests.md index eaffce23..b0fb7385 100644 --- a/pull-requests.md +++ b/pull-requests.md @@ -34,8 +34,7 @@ Documentation for other releases can be found at Pull Request Process ==================== -An overview of how we will manage old or out-of-date pull requests. - +An overview of how we will manage old or out-of-date pull requests.k Process ------- @@ -51,6 +50,10 @@ We want to limit the total number of PRs in flight to: Life of a Pull Request ---------------------- +### Visual overview + + + Unless in the last few weeks of a milestone when we need to reduce churn and stabilize, we aim to be always accepting pull requests. Either the [on call](https://github.com/kubernetes/kubernetes/wiki/Kubernetes-on-call-rotations) manually or the [github "munger"](https://github.com/kubernetes/contrib/tree/master/mungegithub) submit-queue plugin automatically will manage merging PRs. |
