GCC 4.0.2 and PR 23993

[Giovanni Bajo]

Mark Mitchell <mark@codesourcery.com> wrote:

> 1. Release 4.0.2 without fixing this PR.  (The bits are ready, sitting
>    on my disk.)
>
> 2. Apply the patch, respin the release, and release it.
>
> 3. Apply the patch, spin RC3, and go through another testing cycle.

My feeling is that these 4.0 releases are under the reflectors, everybody
looks at them since it's a new GCC cycle and they want to see if it's
getting better or worse. I don't think we should rush bugfixes releases. My
humble opinion is to go with RC3, and possibly test it with Boost to make
sure the static data member patch didn't totally break it. It would be
unfortunate to regress too much in bugfix releases.
-- 
Giovanni Bajo