Thread:Manuel de la Fuente/@comment-188432-20180131003442

How do you avoid bumping up against a reviewer? Great question. There are no real rules because it's simply a matter of unpredictable timing.

If I've formally started the review process, get called away to look at something else, and then come back to find you've entered three more revisions, I face a dilemma. Officially, the rules at Help:JavaScript review process say I'd review the initial revision and then go for the latest one. Sometimes that means rejecting the first one to look at the latest one. Sometimes it won't. It's really a situational thing.

But that's the case of the software telling me as the reviewer that I need to finish up one review before starting another.

You encountered that once, but you also had a different thing. I remember an instance of a review request three or four revisions back from a current revision that hadn't been submitted for review. All of them were made within a few hours, so in a case like that, I'm going to think that the situation is fluid and volatile. So I'll reject the older revision to await the next submission.

In other cases, I've approved an old revision because it's an obvious step forward that has no real issues. Again, it just really depends.

Whatever the case, please don't think you're annoying us by contributing too quickly. We'll let you know, as I once did, if you need to put a hold on your contributions to give us time to do a full review of your work. You're never inconveniencing us by submitting multiple revisions. We like that you're enthusiastic enough to keep improving your code. It's just that there may be occasions where you're submitting faster than we can reasonably review. But I can no more predict what's "too fast" than I can imagine what it might mean for my trusty hound to give me "too much" affection. 