> > Why not check your backlog for your answer? Or do you need me to write > a script to scan all the pending review requests for you?
OK, i just looked at your pending patches: https://reviews.apache.org/users/wangcong/?show-closed=0 The associated tickets: https://issues.apache.org/jira/browse/MESOS-4740 https://issues.apache.org/jira/browse/MESOS-2769 https://issues.apache.org/jira/browse/MESOS-2799 (Some of the rb request does not have associated tickets) I don't see a shepherd for MESOS-4740. Looks like Vinod is the shepherd for MESOS-2769. MESOS-2799 does not have shepherd as well, but I think that should be me. Are you still interested in shipping those patches? I think you made a valid point that there is some problem regarding: 1) Do we want to work on all created tickets (i.e., how do we decide if we want to accept a ticket or not), and who decide that? 2) Once we accept the ticket, how can we prioritize those tickets? Should PMC members groom the accepted tickets regularly? 3) If no committer is volunteer for the accepted ticket, what's the procedure in that case, should we pick one? 4) What's the procedure of finding another shepherd if the original shepherd does not have time for that anymore. - Jie On Wed, Mar 16, 2016 at 2:32 PM, Cong Wang <[email protected]> wrote: > On Wed, Mar 16, 2016 at 2:21 PM, Jie Yu <[email protected]> wrote: > > I understand your frustration. I am curious what review/ticket are you > > talking about, and who is the shepherd for your review/ticket? > > > Why not check your backlog for your answer? Or do you need me to write > a script to scan all the pending review requests for you? > > > > > > Mesos project has a clear guide how to contribute to the project, that's > > what the community has agreed on: > > > > > https://github.com/apache/mesos/blob/master/docs/submitting-a-patch.md#before-you-start-writing-code > > > > I assume this doesn't apply to your committers, at least BenM: > > commit 152ac2b13916bcf2bb9e52accc4951c3ce5bfd76 > Author: Benjamin Mahler <[email protected]> > Date: Sun Feb 21 14:22:07 2016 +0100 > > Log the shutdown duration in the executor driver. > > commit 1488f16d283f69b7dc96feaee91b04a09012ca4a > Author: Benjamin Mahler <[email protected]> > Date: Sat Feb 20 17:35:30 2016 +0100 > > > Added TASK_KILLING to the API changes in the CHANGELOG. > > > commit 978ccb5dd637f0e1577ecae1e21973f50429b04c > Author: Benjamin Mahler <[email protected]> > Date: Sat Feb 20 17:28:58 2016 +0100 > > > Added docker executor tests for TASK_KILLING. > > > commit ee86b13633a9469629dbd79681d0776b6020f76a > Author: Benjamin Mahler <[email protected]> > Date: Sat Feb 20 16:18:22 2016 +0100 > > > Added command executor tests for TASK_KILLING. > > > commit 25d303d8743b524c92627d48f7dfb7ac2a921ede > Author: Benjamin Mahler <[email protected]> > Date: Sat Feb 20 15:31:28 2016 +0100 > > > Fixed health check process leak when shutdown is called without > killTask. > > > > > "Find a shepherd to collaborate on your patch. A shepherd is a Mesos > > committer that will work with you to give you feedback on your proposed > > design, and to eventually commit your change into the Mesos source tree." > > > > This doesn't work, and it needs to change. I already state my reason in the > previous reply, which is just ignored, yeah, like many other requests. >
