Architecture usertags
Hi, I've often thought that it would be useful to have tags in the BTS so that users or maintainers could mark a bug as specific to a particular architecture. This way, when I have some spare time, I could go to the BTS, fetch a list of bugs that are specific to an architecture I care about, and see what I can do about them, or give some feedback if that would help. Using a set of usertags under my own email address on the BTS wouldn't really work for that, since it kindof defeats the whole purpose; I want to use these tags to find bugs that I care about in the first place, but in order for me to be able to add a usertag, I would have to know about the bug before I could find it. Kind of a chicken-and-egg problem. So I suggested to Don Armstrong that he add a set of architecture-specific regular tags; but he seemed averse to this, as the current informal policy of the debbugs maintainers is to require that a usertag is used for a particular purpose before they add a new regular tag; this is so that no tags get created which won't be used. I guess this is a worty goal. After a short discussion on IRC, we came up with another option: a set of publically documented usertags, the definition of which would be announced on debian-devel-announce and linked to from the BTS homepage, so that maintainers could apply them to architecture-specific bugs when necessary. The format, suggested by Steve Langasek, was to use the porters mailinglist as the user, and the architecture name as the usertag (e.g., 'debian-m...@lists.debian.org' as user, and 'm68k' as tag). Before I'll fire off an email to d-d-a announcing that, does anyone have any comments, objections, or suggestions to improve this proposal? Thanks, -- Home is where you have to wash the dishes. -- #debian-devel, Freenode, 2004-09-22 signature.asc Description: Digital signature
Re: Architecture usertags
Wouter Verhelst wrote: Hi, I've often thought that it would be useful to have tags in the BTS so that users or maintainers could mark a bug as specific to a particular architecture. This way, when I have some spare time, I could go to the BTS, fetch a list of bugs that are specific to an architecture I care about, and see what I can do about them, or give some feedback if that would help. Using a set of usertags under my own email address on the BTS wouldn't really work for that, since it kindof defeats the whole purpose; I want to use these tags to find bugs that I care about in the first place, but in order for me to be able to add a usertag, I would have to know about the bug before I could find it. Kind of a chicken-and-egg problem. So I suggested to Don Armstrong that he add a set of architecture-specific regular tags; but he seemed averse to this, as the current informal policy of the debbugs maintainers is to require that a usertag is used for a particular purpose before they add a new regular tag; this is so that no tags get created which won't be used. I guess this is a worty goal. After a short discussion on IRC, we came up with another option: a set of publically documented usertags, the definition of which would be announced on debian-devel-announce and linked to from the BTS homepage, so that maintainers could apply them to architecture-specific bugs when necessary. The format, suggested by Steve Langasek, was to use the porters mailinglist as the user, and the architecture name as the usertag (e.g., 'debian-m...@lists.debian.org' as user, and 'm68k' as tag). Before I'll fire off an email to d-d-a announcing that, does anyone have any comments, objections, or suggestions to improve this proposal? Thanks, Excellent news.This will come very handy.Thanks. -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Architecture usertags
On Tue, Mar 03, 2009 at 10:03:18PM +0200, Vasilios Karaklioumis wrote: > Wouter Verhelst wrote: >> Hi, >> >> I've often thought that it would be useful to have tags in the BTS so >> that users or maintainers could mark a bug as specific to a particular >> architecture. This way, when I have some spare time, I could go to the >> BTS, fetch a list of bugs that are specific to an architecture I care >> about, and see what I can do about them, or give some feedback if that >> would help. >> >> Using a set of usertags under my own email address on the BTS wouldn't >> really work for that, since it kindof defeats the whole purpose; I want >> to use these tags to find bugs that I care about in the first place, but >> in order for me to be able to add a usertag, I would have to know about >> the bug before I could find it. Kind of a chicken-and-egg problem. >> >> So I suggested to Don Armstrong that he add a set of >> architecture-specific regular tags; but he seemed averse to this, as the >> current informal policy of the debbugs maintainers is to require that a >> usertag is used for a particular purpose before they add a new regular >> tag; this is so that no tags get created which won't be used. I guess >> this is a worty goal. >> >> After a short discussion on IRC, we came up with another option: a set >> of publically documented usertags, the definition of which would be >> announced on debian-devel-announce and linked to from the BTS homepage, >> so that maintainers could apply them to architecture-specific bugs when >> necessary. The format, suggested by Steve Langasek, was to use the >> porters mailinglist as the user, and the architecture name as the >> usertag (e.g., 'debian-m...@lists.debian.org' as user, and 'm68k' as >> tag). >> >> Before I'll fire off an email to d-d-a announcing that, does anyone have >> any comments, objections, or suggestions to improve this proposal? >> >> Thanks, >> >> > Excellent news.This will come very handy.Thanks. +1 -- dann frazier -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Architecture usertags
On Tue, 03 Mar 2009, Wouter Verhelst wrote: >The format, suggested by Steve Langasek, was to use the > porters mailinglist as the user, and the architecture name as the > usertag (e.g., 'debian-m...@lists.debian.org' as user, and 'm68k' as > tag). Or debian-po...@lists.debian.org as user. -- | .''`. ** Debian GNU/Linux ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Architecture usertags
On Thu, Mar 05, 2009 at 11:22:19AM +0100, Peter Palfrader wrote: > On Tue, 03 Mar 2009, Wouter Verhelst wrote: > > >The format, suggested by Steve Langasek, was to use the > > porters mailinglist as the user, and the architecture name as the > > usertag (e.g., 'debian-m...@lists.debian.org' as user, and 'm68k' as > > tag). > > Or debian-po...@lists.debian.org as user. I did not think that would be a good idea, since the AFAIK the bts will send out a mail to the mail address listed as user when a usertag is set; it is okay if adding a 'powerpc' tag causes a mail to be sent to the powerpc mailinglist; I do not think it is okay if that would cause a mail to be sent to _all_ porter mailinglists. -- Home is where you have to wash the dishes. -- #debian-devel, Freenode, 2004-09-22 -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Architecture usertags
On Tue, Mar 03, 2009 at 08:52:03PM +0100, Wouter Verhelst wrote: > After a short discussion on IRC, we came up with another option: a set > of publically documented usertags, the definition of which would be > announced on debian-devel-announce and linked to from the BTS homepage, > so that maintainers could apply them to architecture-specific bugs when > necessary. The format, suggested by Steve Langasek, was to use the > porters mailinglist as the user, and the architecture name as the > usertag (e.g., 'debian-m...@lists.debian.org' as user, and 'm68k' as > tag). For Alpha, there is already something like this, although with several tags documented here: http://wiki.debian.org/AlphaBugs Falk -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Architecture usertags
On Tue, Mar 03, 2009 at 08:52:03PM +0100, Wouter Verhelst wrote: > so that maintainers could apply them to architecture-specific bugs when > necessary. The format, suggested by Steve Langasek, was to use the > porters mailinglist as the user, and the architecture name as the > usertag (e.g., 'debian-m...@lists.debian.org' as user, and 'm68k' as > tag). Armel has already been using something similar: http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-...@lists.debian.org&tag=eabi usertags would certainly be used a much more if there were a easy way to set/search them on BTS web interface. -- "rm -rf" only sounds scary if you don't have backups -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Architecture usertags
so that maintainers could apply them to architecture-specific bugs when necessary. The format, suggested by Steve Langasek, was to use the porters mailinglist as the user, and the architecture name as the usertag (e.g., 'debian-m...@lists.debian.org' as user, and 'm68k' as tag). Armel has already been using something similar: http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-...@lists.debian.org&tag=eabi usertags would certainly be used a much more if there were a easy way to set/search them on BTS web interface. And GNU/kFreeBSD also have already something similar: http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=kfreebsd;users=glibc-bsd-de...@lists.alioth.debian.org Or better grouped http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=kfreebsd;users=glibc-bsd-de...@lists.alioth.debian.org;pri0=pending:pending,forwarded,pending-fixed,fixed,done,absent;ttl0=Outstanding,Forwarded,Pending%20Upload,Fixed%20in%20NMU,Resolved;pri1=pending%3dpending%2btag%3dwontfix,pending%3dpending%2btag%3dmoreinfo,pending%3dpending%2btag%3dpatch,pending%3dpending%2btag%3dconfirmed,pending%3dpending;ttl1=Will%20Not%20Fix,More%20information%20needed,Patch%20Available,Confirmed,Unclassified;ord1=2,3,4,1,0,5 Petr -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
