corrections and release plan

A few corrections for some mis-conceptions
- the regressions in 3.4.3 were not due to my use of AI, the regressions were entirely my fault and stemmed from the low coverage test suite and the fact that you can't do a beta release of a security fix. I didn't create the new greatly expanded testsuite till after I released 3.4.3.
- all the regressions I am aware of are fixed in master now

To make this less likely to happen in the future I am planning on creating a rsync security mailing list. It will be private, and I will invite some of the people who reported regressions to join. Those on the list will have access to future security releases before release. The tricky part will be avoiding getting someone on the list who decides to just publish while we're in embargo or is an active bad actor. The xz/Jia Tan episode is a clear warning.
If you think you would be a good candidate to be on this list then get in touch via rsync.project@gmail.com. Then we'll need to work out how to vet you. I will likely want to do a video call and if possible get someone I know and trust to vouch for you. The old days of gpg key signing parties come to mind, I haven't done one of those for over 20 years ...