Ken, et al. I think I should add something else to the previous email.
We also upgrade our training server about 6 months prior to when we plan to upgrade. This keeps us about 1 release behind. Staff get to test the upcoming release on the training server with close to recent/real data. I also keep training up to date with recent point releases, so that means I'll do a mini-update from 3.2.3 to 3.2.4 later this week. We used to upgrade twice per year, but I think we're moving to just 1 per year, which also means skipping releases. For instance, we're going from 3.0.13 to 3.2.[45] at our next upgrade. And, when I talk about testing, I mean it. It is imperative that you test the database upgrade script with a recent copy of your actual, production data. Upgrades of Evergreen are not something that you just do, they require planning and preparation, otherwise you could be facing days of down time and unhappy users. HtH, Jason
