Gunnar wrote:
> Nando wrote: > > PS: I'm not too sure how to handle the new trac service and the list, > > is it ok to use both and duplicate, or is there a better (or > > preferred) way ? Good question. > Clearly it's not attractive to double-post everything, if only because > of the extra work, so I would propose these guidelines: > > General information, questions and discussions: only list > Severe bugs (crashing, failing to build, etc.): both list and trac > Normal and trivial bugs: only trac > Controversial patches: both list and trac > Normal and trivial patches: only trac > Bug reports and patches from external people: whichever > > Let me stress that this is only a proposal and only guidelines. There > will surely be reasons to ask the list about issues previously only > filed on trac or to move discussions from the list over to trac. > > What do other people think? What I would prefer to avoid is that discussion on an issue gets split between the mailing list and trac. So maybe it should be made clear whether the mailing list post is just a pointer to the trac ticket, or the trac ticket is a pointer to the mailing list thread so that it won't be forgotten. Otherwise the above list makes sense to me. Arend _______________________________________________ gnugo-devel mailing list gnugo-devel@gnu.org http://lists.gnu.org/mailman/listinfo/gnugo-devel
