On Mon, Aug 02, 1999 at 04:10:54PM +0200, Richard Braakman wrote:
> Joseph Carter wrote:
> > > > While the bug is important (because what the script does is something it
> > > > really should not be doing), it should not be considered release critical.
>
> Joseph Carter also wrote:
> > It's marked important because there is no way to mark a bug as "seperate
> > this bug from the lot of the rest on the BTS page under my name" and
> > because it risks some form of data corruption. This is of course never
> > acceptable and is most certainly release critical.
>
> Well, consider me confused :-) Which is it?
I mistyped the first time. It should not be removed on freeze if I can't
close the bug before then, however the package DOES need another upload
(warning people of the problem) before release. Once there is a warning
in the package about the feature being dangerous, I will downgrade the
bug.
Of course the time I have spent answering this mail because you are
dissatisfied with my use of the BTS for my packages could have better been
spent trying to write an insert() function for epic which would allow the
bug to be closed, not simply downgraded. I don't mean to be short with
you about it but I _DO_ have my reasons for these things...
--
Joseph Carter <knghtbrd@debian.org> Debian GNU/Linux developer
GnuPG: 2048g/3F9C2A43 - 20F6 2261 F185 7A3E 79FC 44F9 8FF7 D7A3 DCF9 DAB3
PGP 2.6: 2048R/50BDA0ED - E8 D6 84 81 E3 A8 BB 77 8E E2 29 96 C9 44 5F BE
--------------------------------------------------------------------------
2.3.1 has been released. Folks new to this game should remember that
2.3.* releases are development kernels, with no guarantees that they
will not cause your system to do horrible things like corrupt its
disks, catch fire, or start running Mindcraft benchmarks.
-- Slashdot
Attachment:
pgpc2Px1zEqkR.pgp
Description: PGP signature