On Wed, 20 Aug 2008, Afuna wrote:
On Mon, Aug 18, 2008 at 4:42 PM, PauAmma <[EMAIL PROTECTED]> wrote:
Should there be a flag for those [patches needing early exposure]? Or
is a request on the list or in the IRC channel enough?
Hm about a new flag in bugzilla, right now, we have:
needs-spec
needs-design
needs-patch
(needs-testing?)
needs-review
Actually, it would need a different name, because "needs-testing" is for
patches that were already committed and need testing on the staging
server. (Sez Mark.) Perhaps "early testing" or "mass testing"?
If I understand right, the new flag you're proposing would fit after
the needs-patch step, but before the needs-review step
Before or in parallel.
(needs-review I'm taking to be Mark officially reviewing the patch for
committing into the codebase.
It includes that, but I don't see any reason why it should be limited to
that. (Eg, if someone else is working in an overlapping area of the code,
they may want to have a look. Or if it creates a dependency with another
bug, maybe because it uses DW::Request in a way that doesn't work yet, but
that will work when another bug is fixed.)
I think that could work, but I worry that without any way to notify
interested parties explicitly, the patch could just sit there and be
ignored.
True, but that's also true of the current needs-testing.
Currently, volunteers interested in testing a bug can choose to watch
a particular bug they're interested in, and then step forward to offer
to look once a patch is uploaded to bugzilla and submitted for review.
However, I don't think this is scalable. The tester needs to remember
to watch each bug they're interested in; either that, or they'd need
to choose to be notified of all activity, on all bugs, in bugzilla.
Could also do a (shared?) bug search for that keyword and subscribe to the
atom feed (http://www.dwscoalition.org/docs/en/html/query.html#list).
Doing a shout-out on IRC, or over here in DW-discuss could be better
for pinging potential testers, but possible problems: I think that not
everyone interested hangs out in IRC, and that it could potentially
get spammy if posted on dw-discuss. It's less spammy if only the
original shout-out is posted to the list, and all other discussion is
done either through one-to-one correspondence, or on the bugzilla
report itself, but I'm still worried that the additional volume could
force other subscribers to start tuning out all mail from dw-discuss.
Maybe another mailing list for discussing code? Or one for coding
specifically, and one for testers?
_______________________________________________
dw-discuss mailing list
[email protected]
http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss
