-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Op 22-03-2008 om 14:11 schreef Frans Pop: > On Saturday 22 March 2008, Geert Stappers wrote: > > The procedure I follow aims for closing the B.R. ( I known that a better > > aim, is solving the issue ) When I think it can be closed, I close the > > BR. When in doubt, I update old bugreport reports with "No feedback in a > > long time. With a scan over a few months and still no update, it is OK > > close this bugreport." > ~ [Some bully did see a red flag] As long as a bug report is valid, it should not > be closed. Only if it cannot be determined whether it is valid, would > closing become an option. > > The fact that an issue has not been dealt with can be more an indication of > the fact that nobody is sufficiently interested to really look into it than > that the issue does not exist. > Closing such bug reports would only result in that information being lost.
So now how to get back to the real issue: many open bugreports for installation-reports? One way to go is to ignore / neglect bugs no-one cares about. But that is in my opinion to the wrong way, it will backfire us. Thing I want to do, is close all installation reports that were filled be the annouce of lenny beta 1. Other proposals are also welcome. Cheers Geert Stappers -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFH5RM/OSINbgwa/7sRAghIAJ4paspD8iRdA2iNAEdgw3d14JT1pACfXDKb jxngzEzp90z9BoRG6ZKyhzE= =WmfV -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
