On Mon, 8 May 2017, Adrian Bunk wrote: > Doing that per-package would be the worst possible option, > there should be one place (mailing list or BTS query) for > getting all bugs.
Absolutely not! It’s fully reasonable to track all bugs, backported or not, in the BTS. The reason this policy exists in the first place is that historically, bpo was not part of Debian, backporters were not maintainers, and maintainers did not want to get spammed by problems from broken backports. > >... > > 4. Due to the above, I believe a short-circuit/knee-jerk reaction > > to force reportbug to deliver _all_ bpo bugreports to the bpo > > mailing list is wrong, and this should at the least be tagged > > with stretch-ignore and discussed more broadly. > > What you call "short-circuit/knee-jerk reaction" is the official policy: You nicely cut off the quote from me at the wrong point. I wrote that, by adding the Bugs: header to debian/control, reportbug happily forwards bugs to the mailing list instead of the BTS, and as such it’s the responsibility of each backporter (and/or user) to do that, NOT of the tool. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg _______________________________________________ Reportbug-maint mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
