From: Daryle Walker (darylew_at_[hidden])
Date: 2003-10-12 00:37:21
On 10/7/03 4:25 PM, "Thomas Witt" <witt_at_[hidden]> wrote:
> This is going to be a fatstrack review. Fasttrack reviews have been
> introduced as a lightweight process in order to ease the acceptance of
> small utilities. I've put a more detailed description at the end of this
> 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?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk