o The regression from 7.6 is pretty bad. It's therefore fairly important that a fix gets out before 7.8 use gets even more spread.
This only says that a fix should be released soon. The options now was either
A) Release 7.8.316 now, and 7.8.X later with the fix B) Don't release 7.8.316, and 7.8.X later with the fix
Not releasing 7.8.316 does not make 7.8.X ready for release any sooner.
o The fix was already committed (with testsuite tests) well in advance of the final release date. 7.8.324 would have contained it and still be without the Nettle 2.0 stuff. It could have been released instead.
No. 7.8.324 has not undergone beta testing. When 7.8.324 has been beta-tested, it can be released. Releasing 7.8.316 does not limit the possibility to do so.
o The release has been held up for much more petty stuff than this.
Which is bad. Two wrongs don't make a right.