Re: [boost] Release/bug tracking procedures (Was: [1.34.0] failed tobuild on cygwin)

From: John Maddock (john_at_[hidden])
Date: 2007-05-15 05:01:17

Vladimir Prus wrote:
> May I also bring the example of optional? How comes that some
> critical bug was discovered day before hard code freeze?

I don't know what happened in that case, but sometimes bug reports just 
plain arrive at the most incomvenient times....

> While bugs are introduced and fixed by particular persons, most
> projects
> have mechanism to identify what bugs are critical for the next
> release,
> and nudge the right persons into fixing the *right* bugs. It's not
> exactly trivial to come with working procedures for Boost, due to
> great
> variety of components and target environments, but it still necessary
> to try.

Hopefully Trac's milestones feature will help us get this in better order.

John.