One thing to consider is whether or not we can implement a group of committed reviewers to spend time ensuring that patches get tested and marked RTBC via the committee.
thoughts?
-t
--
Tony Guntharp
Co-Founder SourceForge.net
fusion94@damagestudios.net
1-415-692-5507
1-415-680-5361
In regards to this - I did try to highlight to the devel list
small/discrete features that were marked RTBC, but possibly
overlooked: http://groups.drupal.org/node/4943
Probably it was too little too late, and perhaps points out what a
valuable service Augustin provided during the D5 cycle. Maybe
recruiting a couple people (especially those interested in
contributing but without the desire to file/review core patches) to
compile such analyses of the issue queue during the D7 cycle would
help the process?
-Peter
On 7/3/07, Chris Johnson <cxjohnson@gmail.com> wrote:
> In my experience, often RTBC patches which are many weeks old just
> didn't get the attention and general approval of the appropriate
> influential developers. The code can be perfect, the design can be
> perfect, but if the issue isn't interesting, the patch can languish.
>
> I should like to note that this has improved over the years, so we are
> at least heading in the right direction.
>