Hello mentors, I have a bug (#406121), which I don't want to fix before the release (it's minor). Is there a way to tag it as such? Or should I just add a message to the report (I just did) and do nothing else? I'm just thinking that I could mark it as blocked by some Etch-release pseudo-bug (which would have to be created). Is that a sensible idea? The reason I want to mark this in a computer-readable way (as opposed to a textual message to the report), is that that would allow programs to present lists of "fixable" bugs in a better way. Whenever I see lists of bugs (usually RC), they are way too long, and contain lots of things I can't help with anyway (and in some cases, nobody can). Some facilities to get shorter lists with only relevant bugs would be nice. Of course I could also wait with tagging these things until the programs for producing the shorter lists actually exist. :-) Thanks in advance for your thoughts and advice on this, Bas Wijnen -- I encourage people to send encrypted e-mail (see http://www.gnupg.org). If you have problems reading my e-mail, use a better reader. Please send the central message of e-mails as plain text in the message body, not as HTML and definitely not as MS Word. Please do not use the MS Word format for attachments either. For more information, see http://pcbcn10.phys.rug.nl/e-mail.html
Attachment:
signature.asc
Description: Digital signature