Development plan (was: Re: splitting this list)

[Benjamin Kosnik]

>When 3.3 should have been in bug fix mode (ie. stage 3), everybody was 
>playing with their own branches.  Now that all those branches have been 
>merged. there still is no clear plan.  OK, so you cannot plan the 
>details because you cannot demand volunteers to only hunt/fix bugs and 
>stabilize the trunk.  But with a complete lack of a plan like the 
>current situation, a volunteer wouldn't even know what to do or what to 
>prioritize.

Nobody working on gcc can plan or prioritize. I don't think it's just
you, or just me. (Although apparently not too many people care about
trying to fix this, which is discouraging.)

Maybe the release manager could explain what is going on? Once 3.4
branches, is Mark going to be doing the release management for that
branch, and will Gaby then be doing the release management for
subsequent 3.3 releases?

It would be nice if there was a month notice before the 3.3.1 release,
and a two week hard freeze, like Gaby did for the 3.2.3 release. Then
volunteers can actually schedule work.

-benjamin