[development] Perm for setting RTBC - Re: RTBC - how does it work?

Gerhard Killesreiter gerhard at killesreiter.de
Mon Jul 2 17:21:44 UTC 2007

Hash: SHA1

Augustin (Beginner) schrieb:
> On Tuesday 03 July 2007 00:58, Dries Buytaert wrote:
>> On 02 Jul 2007, at 17:12, Augustin (Beginner) wrote:
>>> Right now, the guy who registered two hours ago could bump any half-
>>> cooked
>>> patch onto Dries' lap.
>> If the patch is obviously braindead, someone will mark it as 'code
>> needs work'.  For now, I want every one to be able to mark patches as
>> RTBC.  It's not because you haven't been around long enough, that you
>> can't tell a good patch from a bad patch.
> What I was proposing was one more way to help with the situation.
> It is obvious that you three cannot cope with the work load:
> http://drupal.org/project/issues?page=3&projects=3060&states=14

I've just taken 5 minutes to

1) won't fix 2 issues for 4.6

2) set another patch to "needs work" since Dries didn't want to commit
it as this.

and all of a sudden there are only 3 pages left...

The problem isn't so much that the core committers can't go through the
many patches, the problem is that they are a bit shy to change status on
stuff that doesn't belong there...

Version: GnuPG v1.4.6 (GNU/Linux)


More information about the development mailing list