Re: Re: [RFC] GitHub Pull Requests Triage Team

From: Date: Mon, 04 Jan 2016 22:02:32 +0000
Subject: Re: Re: [RFC] GitHub Pull Requests Triage Team
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to internals+get-90011@lists.php.net to get a copy of this message
Hi! > Warn at 2 weeks, close at 4? There's no real harm in closing it unmerged: > the submitter can always resubmit. That sounds way too short. I mean if we did process all worthy pulls in matter of days, then fine (but see below) but we are very far from that. And when we take a long time to get to it, we should allow some leeway for them to respond too. So I'd say a year-old stale pull is might be too old, but 1 month seems to be too soon. Somewhere between those should be the optimal point :) And I think RFC pulls should have longer time. Of course, people should rather work in their private forks, but some people feel more comfortable collaborating in pulls, and some RFC pulls take way longer than 4 weeks, and people may take breaks and come back. Having a handful of long-lived open pulls is not too much trouble. -- Stas Malyshev smalyshev@gmail.com

« previous php.internals (#90011) next »