On Monday 18 April 2011, Ralf Wildenhues wrote: > * Stefano Lattarini wrote on Mon, Apr 18, 2011 at 12:07:14PM CEST: > > JFTR, here are the things that IMHO we must do for the next release: > > Right now, I'm aiming at 1.11.2, not 1.12. > Ah, I didn't get that. Consider my seggestions moot for what concerns 1.11.2.
> The minimum for the former is *no* additional features. > The important thing is no regressions, not > really any new feature. I might be talked into reviewing ACLOCAL_PATH > support for that, and maybe a couple of the other issues that fix bugs > are safe enough (esp. we could think about deprecating ansi2knr), but > other than that I'd be rather cautious. I want 1.11.2 to be pluggable > for everyone that uses 1.11.1, without *any* thinking (i.e., distros > should be able to just drop it in). > > Your list aims for 1.12. We definitely should try to have that appear > within a reasonable time frame, too, if only because it's been so long > in the making already. However, just only fixing existing regressions > and polishing stuff and testing will take a few weekends, even without > what you've listed. > > For 1.11.2, one thing I need to do is revert v1.11-328-ge87c030 or find > another solution. > > For 1.12, we need to split the testsuite or implement support for > multiple testsuites in one directory. Otherwise MinGW/MSYS won't work. > > Thanks, > Ralf > Agreed on all accounts. Thanks, Stefano
