From: Beman Dawes (bdawes_at_[hidden])
Date: 2003-10-15 18:32:35
At 01:37 AM 10/12/2003, Daryle Walker wrote:
>On 10/7/03 4:25 PM, "Thomas Witt" <witt_at_[hidden]> wrote:
>> About Fasttrack Review
>> What components qualify for a fasttrack review
>> - ---------------------------------------------
>> - The technique must be already in use in boost libraries
>> thus the new component provides a common implementation
>> - The component must be small
>> - ---------
>> - A full boost-conformant implementation is available in the sandbox
>> - The Boost Review Wizard posts a review announcement to the list.
>> Review period should last for 5 days. No two fasttrack review should
>> run in parallel. Fasttrack reviews may run during full reviews, though
>> generally this should be avoided.
>> - After the review period ended, the submitter will post a review
>> summary containing planned changes to the current implementation.
>> - After applying all changes, the component will be checked in to cvs
>> by the submitter.
>This information will be added to the general Boost documentation?
Done. See more/formal_review_process.htm in CVS.
It would be good if Thomas could check the wording in CVS as I made some
mostly editorial changes to his original wording above.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk