From: Thomas Witt (witt_at_[hidden])
Date: 2007-05-13 14:08:36
Vladimir Prus wrote:
> Atry wrote:
>>> As discussed on IRC, this appears to be cygwin-specific bug, making
>>> build on cygwin impossible. Looks like one between RC3 and final
>>> release was a bit too hasty ;-)
>>> I believe the attached patch should fix the immediate problem.
>> Thanks. But I wonder why is this issue been reported one month ago still
>> appeared now? http://lists.boost.org/Archives/boost/2007/04/119537.php
Looks like it wasn't an issue of haste.
> Because we don't seem to have any procedure whatsoever in place that makes
> sure that incoming bug reports are classified with respect to impact on
> next release, and no procedures that make sure all critical issues are
> fixed before release?
Traditionally we did rely on every library maintainer doing exactly that tracking and
making sure everything is in order for release for their own library. Providing
regression tests as a help. This obviously does not work anymore.
It's not procedures that's lacking the most.
-- Thomas Witt witt_at_[hidden]
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk