Re: Bug Tracker notifications?

On Sat, Nov 5, 2011 at 2:42 PM, Stefan Marr <Stefan.Marr@vub.ac.be> wrote: > Hi Ferenc: > > (off-list) > > Feels like a very stupid question to ask, but is there a mailing list, or > another way to get notifications for newly created bug reports? (php.qadoes not seem to be it, > but there seems to be one for the documentation.) > > I typically go once in a while to the bug tracker and search for bugs that > have the keyword 'trait' in it. > > And now I am wondering, whether the bug tracker could actually tell me > about newly reported bugs automatically. > > Didn't know who to ask else, but since you seem to be busy with the > infrastructure currently, I thought you might know. > > Thanks a lot > Stefan > > Hi, Yeah, there is. Most bug emails go to the php-bugs mailing list http://news.php.net/php.bugs I said most, because the setup is a little bit more complicated: - the reporter gets an email - the new assignee(if it was changed) gets an email - the default address for that package get an email. see: http://svn.php.net/viewvc/web/php-bugs/trunk/include/functions.php?view=markup#l892 the last one is the complicated part: http://svn.php.net/viewvc/web/php-bugs/trunk/include/functions.php?view=markup#l1303 - the security and the documentation bugs has their email address "hard coded". - for other bugs we check the bugdb_pseudo_packages table, and use the list_email for the given package - if not list_email is found and the package is a pecl package, we will fetch the package maintainer(s) or send it to pecl-dev@lists.php.net if no maintainer is found - if not list_email is found and the package isn't a pecl package we will send the bug to php-bugs@lists.php.net currently we have the following list_email in bugdb_pseudo_packages: | 3 | 1 | Documentation problem | Documentation problem | php | doc-bugs@lists.php.net | 0 | | 4 | 1 | Translation problem | Documentation translation problem | php | doc-bugs@lists.php.net | 0 | | 5 | 1 | Doc Build problem | Doc Build (PhD) problem | php | doc-bugs@lists.php.net | 0 | | 6 | 1 | Website problem | PHP.net Website problem | php | php-webmaster@lists.php.net | 0 | | 7 | 1 | Online Doc Editor problem | Online Documentation Editor problem | php | doc-bugs@lists.php.net | 0 | | 8 | 1 | Systems problem | PHP.net Systems Operation problem | php | systems@php.net | 0 | | 18 | 1 | PHP-GTK related | PHP-GTK related | php | php-gtk-dev@lists.php.net | 0 | | 160 | 176 | Livedocs problem | Livedocs problem | php | doc-bugs@lists.php.net | 1 | | 171 | 29 | FPM related | FPM related | php | php-bugs@lists.php.net,fat@php.net | 0 | | 170 | 0 | Security related | Security related | php | security@php.net | 1 | | 178 | 1 | Testing related | Testing related | php | php-bugs@lists.php.net,php-qa@lists.php.net | 0 | | 179 | 0 | PECL | PECL | pecl | pecl-dev@lists.php.net | 0 | | 180 | 179 | PECL website | PECL website | pecl | pecl-dev@lists.php.net | 0 | | 181 | 179 | PECL bug system | PECL bug system | pecl | pecl-dev@lists.php.net | 0 | So as you can see most of the mails go to php-bugs, but not all (doc, website, security, systems, pecl, gtk), and there are some, which only sent to inviduals (pecl packages with maintainers). For traits, I would suggest creating a pseudo package, and adding your mail (and php-bugs) to the list_email, that way if the package is correctly set, you will be notified at all times. I'm cc'ing php-webmaster, maybe it can save some time for someone when checking out the bugsweb code. ps: I still think it would be useful if every bug email except security would go to a public mailing list. -- Ferenc Kovács @Tyr43l - http://tyrael.hu