John Maddock wrote:
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....
This happens. My impression is that it's not the case. And probably, we can alleviate this "inconvenient times" effect by introducing two deadlines -- for submitting bug reports, and for code changes, thereby nudging folks into submitting bug reports when there's still time to fix them.
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.
That's my hope too. However, without some practices to make sure milestones are set, and without actually checking list of bugs assigned to milestone, that won't work. - Volodya