[development] Time to take away RTBC from every Joe

Florian Loretan floretan at gmail.com
Thu Feb 21 19:47:30 UTC 2008

If we leave the RTBC permissions as they currently are, a confirmation step
could reduce the number of untested patches that accidentally make it to the
RTBC status. This additional step could be added conditionally based on user
roles so it wouldn't impact usability for those who go through the process
of marking patches as RTBC multiple times a day. The confirmation step could
look like this:

By marking this patch as RTBC (ready to be committed), you confirm that:
- The patch applies to the latest version of the code
- The patch gives the desired result
- The code is clean
- The code is well-documented
If you are unsure about any of the points above, do not change the status of
the patch.

[Keep current status]            [Set status to RTBC]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20080221/5928d4e9/attachment.htm 

More information about the development mailing list