Some projects have a time-based release strategy (e.g. "we release once every six months"). Would it make sense for gcc to do that for all maintenance releases? e.g. leave the current process the same for .0 versions, which users are scared of anyway, but coordinate all other releases to occur once per quarter? -- Wine for Windows ISVs: http://kegel.com/wine/isv