On Sun, Feb 23, 2003, David A. Desrosiers wrote: > I've already got this working, but am working out the logistics with > deploying it, but the problem is that bugs reported from nightly builds will > probably be ignored.
It's a complicated issue; we want bug reports, but if they should be of any real use they must be "tagged" with a version number, too. I will never "ignore" bug reports, but I already have my doubts about users adding bug reports to our bug database for the "unofficial" hires versions Adam distributes. Personally, I think the bug database should only include bug reports for official versions. Including bug reports for other versions either built by users using code from CVS or from versions distributed "outside" the normal releases makes it a real PITA to get any useful info from the database and the risk is that "real" bug reports will be "lost" in an ocean of "old" (a.k.a. already-fixed) bug reports if we start to make "nightly" builds. Today, you can indicate that the buggy version used code from cvs. However, that is about as useful as saying it crashed when we had a full moon ;-) The code is changed all the time and to be able to figure out what happened it usually help if you know what code that was used for the "broken" version. I don't really want to "lose" those bug reports, but it would be great if they could be kept out of the bug database. However, I'm not really convinced that there is any reason to distribute new versions every day... /Mike _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
