On Mon, 19 Oct 2009, Joachim Breitner wrote: > @dons: What are your requirements until you will accept this feature on > bugs.d.o, in terms of number of packages or clear consensus on d-devel > or such or actual inclusion in the policy?
Depends on the complexity of me actually getting the information to the bts,[0] but assuming that there's: 1) a clear consensus on the methodology to make/update the links[1] 2) a tab-delineated text file generated somewhere[2] with the source package name in the first field, the link to the upstream bts in the second, and the wiki page on wiki.debian.org for additional bug reporting/triage information in the third 3) enough source packages implementing #1 for me to actually test it; I imagine if we get at least a half dozen packages from different maintainers it'll be enough to demonstrate that it's workable. then I'll shove it into my queue to implement. Don Armstrong 0: the more complexity, the longer it'll take; the actual code change to debbugs is relatively trivial. 1: probably a good idea to also have a draft for inclusion in devel-reference 2: where this is depends on the method, but probably ftpmaster is the ideal place; dunno, though. -- Some pirates achieved immortality by great deeds of cruelty or derring-do. Some achieved immortality by amassing great wealth. But the captain had long ago decided that he would, on the whole, prefer to achieve immortality by not dying. -- Terry Pratchet _The Color of Magic_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
