Hi Mark, you wrote
> Those who have been watching carefully will note that there is no sign of an > actual > 4.0.1 release. since the branch has been frozen for quite sime time now, a lot of patches for the 4.0 branch have piled up. Given the facts that a) we'll have another relaese candidate anyway b) many of these patches have seen some testing on mainline (and some even on the 3.4 branch) c) they fix regressions (some of them are even wrong-code like PR 21850) d) the release would already be outdated otherwise e) if problems showed up with the patches for users we could address them in 4.0.2 and not just 4.0.3 wouldn't it make sense to commit the pending patches? It would be as if you froze the branch a week later ;-) Regards, Volker
