On Sat, 28 Feb 2009, sean finney wrote: > currently, a bug can be tagged as "pending" globally, for all versions of > the package to which the bug applies. however, this isn't so practical > for tracking pending status w.r.t. stable/testing. > > i guess it's assumed that "pending" means "pending to unstable", so > it would be nicer to have a way to say at a more granular level > "pending to stable,testing,unstable", and then of course also to > filter/display bugs based on this. i.e. "show me all the security > bugs against php5/stable that haven't already been tagged pending".
This you can do already using usertags. > i could suggest one approach, though perhaps you may have a better > idea: > > bts command/syntax: > > pending <bug> [dist] > > marks the bug as pending for the particular dist > (stable/testing/unstable or codename). if no dist is specified, > unstable/sid is assumed, which is identical to the using "bts tag > <bug> pending". Pending is a tag, so this won't work. [It'd basically require breaking everything that uses tag pending, and requiring everyone to learn an entirely new syntax.] What it sounds like you're basically asking for is pending-testing, pending-stable and pending-unstable. However, the cases where the latter to are even remotely useful are fairly small, and probably only apply to bugs being prepared for security updates, etc. In such a case, I'd suggest using usertags for a debian-secur...@ldo user (or something else) to track uploads which are pending. Don Armstrong -- Sentenced to two years hard labor (for sodomy), Oscar Wilde stood handcuffed in driving rain waiting for transport to prison. "If this is the way Queen Victoria treats her prisoners," he remarked, "she doesn't deserve to have any." http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
