Posted by catch on July 7, 2007 at 1:17pm
4 followers
Jump to:
| Project: | Drupal.org webmasters |
| Component: | Site organization |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
Following the recent development list discussions, I've been thinking it'd be good to add some extra flags to CNR and CNW (or additional flags, in which case that'd be a feature request againt project.module).
Sometimes patches just need benchmarks:
http://drupal.org/node/148849
http://drupal.org/node/106559
are examples where this has, or will be the case. There's plenty of others as well.
The idea being that along with "concept needs feedback" which is a great idea - there might be a way for the patch statuses to provide more description as to what kind of review (or work) they need.
Comments
#1
I think this is a good idea. If I create a benchmark setup, I usually don't bother to run two more patches. So it would be great to be able to find them easily.
#2
Thanks for the feedback, that was my thinking behind it.
Also maybe:
needs user interface review (cf. http://drupal.org/node/147143 )
- but this might be better done as checkboxes/select which add information to the "needs review/needs work" status, which'd be a different thing entirely.
#3
I agree completely with a "needs benchmark" indicator of some sort.
While list that could be multi-selected (needs benchmark, needs UI review, needs {more criteria} review) would probably be best, I think the simple case is the most likely which is that a patch needs either a benchmark OR a UI review, but rarely more than one at a time.
#4
We now have issue tags. No longer applies.