Re: QA weekly bug summary

Gregory Beaver wrote: > Another very good idea is hidden in your mail, which is to say having > patch notifications sent to pear-qa, so that everyone can see when a bug > has a fix attached to it. I haven't tried to use this patch feature, but it was often requested to have a possibility to attach some *code* to a bug or feature request. Note the word *code*: it includes not only patches, but, for example, also longer code snippets that show how a bug can be reproduced. Sending an email to pear-qa makes IMO only sense for real patches, and in this case also not for actively maintained packages. If somebody sends a patch for one of the packages that I (co-)maintain, he can be sure that gets at least an answer or that I apply the patch. Therefore, an easy solution might be to use the "unmaintained" flag: if it is set, and a patch (or some code) is attached to a bug, then an email could be send to pear-qa. This has only the disadvantage that not every unmaintained package is marked as unmaintained. Regards, Mark -- http://www.markwiesemann.eu