tl;dr as a contributor you should see no difference in the workflow you use to contribute, review, and approve PR's for the kubernetes/community repo
Tide [1] is a thing SIG Testing been working on to replace the submit-queue [2]. It uses github queries instead of webhooks to select pools of PR's instead of an ordered queue of PR's. For more information on why, see the proposal / design doc [3].
We've been using tide against kubernetes/test-infra for ~three months, kubernetes/federation for ~two months, and recently enabled it for (among other repos) kubernetes/kubectl and kubernetes/charts. As I mentioned during SIG Testing's Oct 19 update to the community [4], our goal is to replace the submit-queue for all kubernetes repos.
I would like to do this tomorrow for kubernetes/community [5]
I'm e-mailing kubernetes-dev about this to give you a heads up that this is happening. We recognize tide needs docs [6] and could stand to use a nicer UI before we enable tide on a highly-tested, high-traffic repo like kubernetes/kubernetes. Turning on tide for kubernetes/community will expose it to a larger audience to help get us there.
Questions and feedback welcome.
- aaron