Date: 18 Nov 2002 10:58:32 -0800 From: swear@attbi.com (Gary W. Swearingen) To: Eric Anderson <anderson@centtech.com> Cc: Brad Knowles <brad.knowles@skynet.be>, FreeBSD Chat <freebsd-chat@freebsd.org>, Mark Murray <mark@grondar.za> Subject: Re: FreeBSD: Server or Desktop OS? Message-ID: <jak7jad7s7.7ja@localhost.localdomain> In-Reply-To: <3DD91EC8.3040105@centtech.com> References: <20021116232242.S23359-100000@hub.org> <04f801c28e20$0a3665b0$0a00000a@atkielski.com> <3DD7CF81.7030407@cream.org> <056001c28e60$2af21cf0$0a00000a@atkielski.com> <1037560276.1094.19.camel@skalman.campus.luth.se> <3DD7F107.DCE620A6@centtech.com> <a05200f02b9fdb6ba20c2@[213.136.30.47]> <3DD91EC8.3040105@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Eric Anderson <anderson@centtech.com> writes: > Me too.. I'm willing to organize it and get things going.. You might consider having two parts of "it". There is the testing, which some have already offerred to help with, and it sounds like Eric is willing to organize that. But I suspect what is needed more than that is to organize the resolution of problems detected by both the organized testers and by un-organized testers (AKA "users") so detected problems get fixed (and so developers don't have to spend as much time working with detectors of problems, both real and false alarms). Many people who find bugs in the field don't report them because they don't know about reporting mechanisms (PRs or freebsd-stable) or are afraid to deal with the gurus or have had bad or useless experiences. They are often unsure whether they have seen a bug or maybe it's only configuration or hardware problems. The people on -STABLE don't probably let many problems drop through the cracks unless the user is either very clear about the bug, has a fix, or is very persistant. So if someone is willing to do organizational-type work, I'd think it would be good to organize a team to field such user problems and get the testers to work with the user in duplicating the error in their test systems or determining whether it is a bug or not and have the tester (maybe user too) work with the developers to make sure it gets resolved. This same organization would track the resolution of problems found by organized testing. Maybe the PR system could be used by this organization, using a new value for PR "class" or "category". Users would be told to report OS stability problems to -STABLE (or -CURRENT) (or maybe the team's mailing list) and the team would be expected to get them into their tracking system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?jak7jad7s7.7ja>