On Mon, Jul 13, 2009 at 03:21:27AM +1000, Gavin Baumanis wrote:
> I ping the list asking for review etc.
> But it still doesn't get any interest from a full committer.
> Normally I would send it to the issue tracker.
> At this point - and not before, do I propose that the PM could
> instead, commit the change.
I think the patch should be filed into the issue tracker with
a milestone of either the next .0 release or the next patch release.
If the patch does not address a serious bug in a released version,
then it should be scheduled for the next .0 release.
If the patch does address a bug which exists in a released version
of Subversion, then the issue should be scheduled for the next
We cannot just commit patches which no full committer has looked at
(or partial committer if the patch falls in their area).
That's not in the best interest of ourselves and our users.
When the scenario you describe happens, we have too little developer
resources to handle the submitted patch at the point in time it gets
submitted. It means that people are busy with other things. Just
committing the change anyway is no good answer to the problem of
lack of resources. Putting it into the issue tracker for later handling
is the correct answer, even if it means disappointing the original
submitter because the patch isn't being processed as quickly as they
Keep in mind that we aren't under any obligation to fix anyone's problem
as quickly as we can. This may sound like bad attitude towards our users
and patch submitters, but it's not. Rather, we only have so much developers
with only so much time to pay attention to things, and we usually
have more things on the table than we can pay attention to all at once.
Received on 2009-07-13 14:28:14 CEST