> But you raise a good point: are there people tasked with doing
> QA work, or are we relying on users to submit PRs? I've always assumed
> the latter procedure was what was occuring, if not by design, then by
> necessity.
(I use "we" below to mean "the FreeBSD community"; I use FreeBSD, and
write articles about it, but I by no means speak for anyone with any
decision-making power.)
Having tracked FreeBSD since '95, I can say with a fair amount of
confidence that there is no "dedicated QA" person. Jordan is the
"release coordinator", which seems to be equivalent to "scapegoat" in
this context.
The various committers are held responsible for the quality of their
work. As a regular reader of cvs-all, I can assure you that
developers are quick to step on other people's bogons. ;)
If you, or anyone, has any bright ideas on what a FreeBSD QA engineer
would do, I'm sure people would be all ears. But with the FreeBSD
development process, we certainly can't hold the tree still for a
month. And while I don't work for Walnut Creek, I feel fairly safe
saying that they don't have the financial resources to test each
release on every piece of hardware out there.
This leaves send-pr, and snooping through -stable and -questions.
If we want to increase the quality of our releases, we need to
increase the number of high-quality of PRs we receive. We need to
publicize the procedure for making the ideal pr, and the importance of
doing so.
Hmmm... anyone know a magazine that would be interested in a send-pr
article? My usual market isn't.
==ml
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
