Comment 20 for bug 20142
Revision history for this message
|
|
#20 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
tag 152473 + sid
tag 152791 + sid
tag 162663 + sid
tag 176415 + sid
tag 180149 + sid
tag 181494 + sid
tag 183463 + sid
tag 189422 + sid
tag 190209 + sid
tag 197726 + sid
tag 203412 + sid
tag 213539 + sid
tag 215677 + sid
tag 215923 + sid
tag 227386 + sid
tag 241394 + sid
tag 256402 + sid
tag 257225 + sid
tag 257231 + sid
tag 265344 + sid
tag 280803 + sid
tag 281639 + sid
tag 318206 + sid
tag 320398 + sid
tag 321780 + sid
tag 321781 + sid
tag 321782 + sid
tag 336511 + sid
tag 338564 + sid
tag 339834 + sid
tag 339835 + sid
tag 354695 + sid
tag 360873 + sid
tag 360874 + sid
tag 364026 + sid
tag 365256 + sid
tag 366073 + sid
tag 366087 + sid
tag 366093 + sid
tag 367045 + sid
Thanks, control, and have a nice day!
# Oops, they fixed the case-insensitivity feature!
stop processing, control!
I am tagging all of my bugs "sid", so they will no longer be relevant
with respect to the release. The release team may untag these bugs if
they desire, as long as the presence or absence of this tag does not
affect its severity (as specified under Debian Policy). It is my policy
from this point on to tag all of my bugs with either the "sid" or
"experimental" tag, as the case may be, to prevent them from affecting
the release. As a consequence, since such bugs are no longer relevant
to the release, they are no longer governed by the release team's
policy, but only by Debian Policy. Bugs that would be serious based on
Debian Policy but merely important based etch RC policy (like those
violating section 2.5) can now be treated as serious, as they will not
affect britney.
The proper solution to this bug is to have an "rc" or
("release-critical" or similar) tag which defines which bugs are RC, or
at least a "not-rc" bug. Alternatively, Debian Policy could again
become the authoritative reference for what is release-critical.
In the event you have a problem with this, feel free to bring it up on
debian-project. I am subscribed, so you need not CC me. *DO NOT* untag
these bugs except as specified above without first bringing the issue up
on -project.