From: Richard Jennings (richard.jennings_at_[hidden])
Date: 2005-09-26 08:48:57
On Sat, 24 Sep 2005 11:51:42 +0100, David Abrahams
>> Again, and as I mentioned to John, there are allways room for
>> improvement, but I do think the boost developers do a lot. I bring
>> this up because it is a genuine concern whenever you deal with
>> sub-contractors or whatever, and it also apply to use of open
> I understand the notion of QA in general, but I want to know
> specifically what you think QA should look like, or look more like,
> for Boost.
>> Boost and or Boost Consulting could possibly make a more prominent
>> to QA efforts and procedures on their web sites. At least have a
>> bullet for
>> it an tie together the procedures you have with peer reviews, testing,
>> regression testing, bug tracking, change management, public developer
>> list. Then you can call this web page and its guidelines your Quallity
>> Assuruance Plan.
> Okay, that's a great idea. Boost Consulting's website desperately
> needs an overhaul anyway.
I'm going to need to do a formal assessment of the 'quality' of Boost
and so this caught my eye. I did some more reading on the Boost web site
the review procedures, code guidelines, etc., etc. It seems to me that
has its procedures in place and documented and what would help someone
Boost is a higher profile for them.
So I'd support the idea of a page called something like Quality Assurance
Perhaps a section for library development and one on Boost releases with
to the existing guidelines.
One thing I don't see documented is how review managers are selected
there being a queue which the Review Wizard manages). The peer review
anyone to submit comments and it's up to the review manager and library
author to consider them. How do we know that the review manager has
experience of Boost and C++ (or whatever) to carry out his/her role?
Ultimately it seems that the quality of Boost rests on the experience of
library authors and reviewers, so how does an observer assess that?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk