Experience has taught me that it is quite counterproductive to have the latest version of RocketChat in production. We suffered bug after bug until we got to version 3.12.3 which is pretty stable, so I’m not going to upgrade until after extensively testing the latest version or reading the issues on github before upgrading. My bosses would not forgive me another catastrophic bug like the ones in 3.12.1 and 3.12.2.
Bugs are not fixed as fast as you say, there are certain CSS issues reported months ago, or suggestions already approved by the developers years ago that are still in the pipeline.
By this I don’t mean I won’t upgrade, just that I’ve jumped off the latest version bandwagon. I have to set up a test server and test with the latest version, to see if the same thing happens there and report back.
By Rocket, user is unlocked on the AD, of course. Failing to log in into RC doesn’t lock AD user on the domain.