This is going to be a simple one -- just one patch version (3.2.8 to 3.2.9) -- so it's not going to be too painful. I just prototyped the upgrade in my lab at home with the entire (unrehearsed) process taking perhaps 15 minutes, with most of that the database schema upgrade. I didn't notice any user-facing changes other than having to log in again afterwards, but will suffix that with the fact that I didn't notice anything.
Part of this is to set the stage for an upgrade to the 3.3 branch that's the current production-quality one. However, that may involve user-facing issues like what happened the last time I was forced to do a very major version jump from 3.0.14 to 3.2.8. Stay tuned.
It's going to be close to 60 today, and I'm contemplating getting one of my minis out of its winter tomb...
