On Thu, Jan 15, 2026, at 6:03 PM, Paul Eggert wrote: > On 1/14/26 04:07, Jonathan Wakely wrote: >> Would it make sense to do an Autoconf 2.72.1 release which is >> identical to 2.72 except it fixes this serious incompatibility with >> GCC 16? > > Easier would be to simply release what we've got.
I was thinking the same thing. We have a whole bunch of relatively low- risk patches stacked up in git, might as well call them 2.73. I'd like to see some broad testing first, though. What if I put out an alpha release sometime this week and distribution maintainers do some mass rebuilds with it? Also, does anyone know of any high-importance patches waiting for review, or other high-importance bugs that should be addressed ASAP? zw p.s. Paul, you're just as entitled to turn the release crank as I am :-)
