Brian,
I’ve been around almost since the beginning and I am very aware that most bugs are generated by the continuously requested new features and changes that we are requesting. They appear, then are reported in this forum and corrected in new versions relatively quickly.
This process is fine in about 90% of the cases but for some like myself who have remote sites that require a 2 1/2 hr drive over difficult terrain to get to, it is a problem to go there, update, come home, and find out the version I updated to has a bug and shut down, crashed or whatever. It’s another 2 1/2 drive to reboot, go back to an old version or whatever. These late night drives after work can turn dangerous in the winter. I have done it twice already this week. Some of this can be done remotely but what happens in the end is we never update. There is a version near by in the 7.70’s and it is never going to change because his drive is about 8 hours!
Why not post on the download page a “tested version” that those of use can’t or don’t want to, go through the testing of new versions. As a version becomes used for awhile and bugs appear gone, replace the old tested download version on the download page with the new “tested” version before making any more changes and upgrading.
Does this make sense?
