in my understanding, it's pretty common for discussion about a particular bug/issue to happen on that issue's ticket. that way the discussion can be easily reviewed by anyone working on the issue. referencing threads in mail archives is both inconvenient for those participating in the discussion and for those who review the bug later. it's also likely to be missed at times.
the reason JIRA/bugzilla ticket changes trigger emails to the dev list is so that people on the list can still be aware of the stuff going on in the issue tracker. so, as fas as i'm concerned, the discussions in the tracker *are* on the dev list already. i am a little disappointed by the noisyness of JIRA's emails when you alter a just few fields on an issue (making it difficult to notice exactly what's changed, especially comments added then), but it seems decent enough when it comes to merely adding comments. so... i guess my answer and preference is that so long as a particular issue has a ticket open in the issue tracker, that is the best place for discussion on it. On 9/19/05, Henning P. Schmiedehausen <[EMAIL PROTECTED]> wrote: > I've noticed that with the rush of bug reports into JIRA and also the > following number of comments on the bugs and their reflection to the > -dev list, some discussions moved or are moving to JIRA itself. Is > that intentional or shall we try to keep the discussions on this list > and just reference possible threads from JIRA issues? > > Best regards > Henning > > -- > Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH > [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/ > > RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire > Linux, Java, perl, Solaris -- Consulting, Training, Development > > 4 - 8 - 15 - 16 - 23 - 42 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
