From: Gennadiy Rozental (rogeeff_at_[hidden])
Date: 2007-10-07 17:16:46
Henrik Sundberg <storangen <at> gmail.com> writes:
> 2007/10/7, Jeff Garland <jeff <at> crystalclearsoftware.com>:
> > Gennadiy Rozental wrote:
> > > Additionally it's important to split new failures from regression. New
> > > failures we just mark as expected on day of release and ignore. At the
> > Well, this doesn't quite work for me. If a new library can't pass tests
> > on the 'primary platform list' then it needs to be removed from the
> > release because it's not ready.
> The definition of "New Failure" might be problematic.
> E.g. If a test is added in 1.35, due to a bug found (and not fixed) in
> 1.34, a new failure occurs in the test output.
> If functionality with poor quality is added to an old library, then
> the code should not be accepted, not just marked as an expected
What ff I added feature that works on gcc 4.0, but do not have time to port it
on VC 7.1? I've added corresponding test. No egressions appear. IMO what
should be done is that this test should be marked as expected to fail
everywhere where it fails and next release I'll try to port it to VC7.1. Next
to CW and so on.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk