Thanks for the workflow suggestions. I've been doing this job for quite sometime and I'm well aware of what a beta is and what backups do. I have my stuff on 3 different HDs and there's no chance of me losing anything - I lost nothing here, only a couple of hours.
Also, I'm sure that you are aware that in a busy environment a couple of hours of troubleshooting can be quite a "downer"
Again, I'm not trying to say that something extra horrible happened, I'm just trying to communicate the importance of a changelog.
As for this:
The best solution here is not to use anything which is beta in production flow. It was said many times before. Beta version is only for users, who are willing to play with latest versions and to discover possible bugs. If you want to be sure to get bug-free firmware revisions, use only RELEASE versions and not BETAs.
2.4 was originally intended to be a RELEASE version, that's why it was a requirement for the RM. It was IMPOSSIBLE to use a RELEASE version of the firmware with the RM. It was beta or nothing.
Guys, it was obviously a MISTAKE by the KPA team. Nothing horrible. YES THEY DO MAKE MISTAKES, just admit it
I'm not saying they are idiots for making a mistake, I'm saying they should keep a changelog. That's it. Stop beating a dead horse.