I've been running the release candidate since shortly after it was delivered and have not found any significant issues.
While preparing the changelog for 2.332.2, I realized that there is a mention of remoting 4.13 in the backporting commit
https://github.com/jenkinsci/jenkins/pull/6401 but I don't see remoting 4.13 being included in the release candidate build. The "About" page shows that it includes remoting 4.12.
What is the consequence if Jenkins 2.332.2 includes remoting 4.12 (as 2.332.1 did) rather than remoting 4.13?
Websocket agent does not reconnect (
https://issues.jenkins.io/browse/JENKINS-66446) is the issue in the pull request that mentions remoting 4.13. I've not been testing websocket agents, so I don't think that I would see the issue in my environment.
Mark Waite