From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-06-06 23:10:27
Beman Dawes wrote:
> By definition, the last release is always considered stable. Stable
> doesn't mean perfect, it just means good enough to build upon.
OK, but that isn't what I understood from your description:
> The definition of stable includes passing all regression tests on
> release-critical compilers (or marked up accordingly), and also
> passing all other stability measurements. If a library depends on
> other libraries, it is only stable if those libraries are stable.
> Stability criteria include not only regression test failures, but
> also inspection failures, tool-chain errors, configuration errors,
> missing files, and any other detectable errors that reduce release
> quality or impact development environment stability.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk