Peter Eisentraut <peter_e@gmx.net> writes:
> Last I checked 2.51 was also released. AC 2.50 had some quality issues in
> my mind which were probably fixed by now. If we see a need we can update;
> I suppose it depends on the release schedule. (Note that some non-trivial
> patches will be needed before 2.5x will work on our configure.in. I have
> these mostly worked out.)
I think it's your call whether to do it now or wait. It'd be nice not
to have the project's version of Autoconf be a moving target, however
--- if the various developers who commit configure changes don't all
have the same Autoconf that's on hub.org, we have problems. If you
think there's likely to be a 2.52 soon, maybe we should wait.
Another thing to ask is what the newer autoconf will buy us. I remember
you mentioning some things that sounded nice, but I forget details.
As far as schedule goes, I'm still thinking 7.2 beta by the end of
August, but that's just MHO.
regards, tom lane
