[development] RTBC - how does it work?

Dries Buytaert dries.buytaert at gmail.com
Tue Jul 3 18:00:12 UTC 2007

On 03 Jul 2007, at 18:35, Jeff Eaton wrote:
>> if an RTBC is marked as
>> a "bug" and has, say two or three reviews from
>> "trusted reviewers" can't these just be committed "as
>> is" without core eyes on the patch?
> This still happens. It's worth noting, however, how *many* large- 
> scale architectural patches went into D6, and how many of the  
> patches still in the queue at the time of code freeze were  
> architecture level. The bug fixes you refer to above can still be  
> committed after code freeze, too. :)

Drupal development is always going to be a bit broken and because of  
that, not all patches will get the attention that they deserve.  I  
recognize that this can be frustrating, and we'll work on that.

However, like Jeff, I'd like to encourage all of you to look at the  
bigger picture too -- and maybe to compare our performance to that of  
other Open Source projects.

I think we did a _great_ job during the Drupal 6 development cycle.   
Plenty of important architectural changes made it into Drupal 6, and  
there aren't that many open issues that strike me as crucial.  In  
addition to some sweeping changes, hundreds of patches made it into  
Drupal 6.  And during the code freeze, many more patches will land.

Despite some frustration during the code freeze, this looks very much  
like a job well done.  Therefore, I don't think the system is  
fundamentally broken or doomed as some people try to make us  
believe.  There is room for improvement, but let's not neglect the  
fact that we did a really great job.


Dries Buytaert  ::  http://www.buytaert.net/

More information about the development mailing list