Matthias, I understand your concerns and wish we wouldn't be in that situation. The options are now:
1/ Update fetchmail to a completely new version (6.3.16) once the release is out
2/ Fix the critical issues as part of the SRU process (6.3.9+patches)
Given the policy, I expect the SRU team to reject the global change to 6.3.16 and support solution (2), but that's their final call.
Matthias, I understand your concerns and wish we wouldn't be in that situation. The options are now:
1/ Update fetchmail to a completely new version (6.3.16) once the release is out
2/ Fix the critical issues as part of the SRU process (6.3.9+patches)
Given the policy, I expect the SRU team to reject the global change to 6.3.16 and support solution (2), but that's their final call.