Joseph Craig wrote:
While this post has almost nothing to do with the thread, it does. If you are operating a production website, your business depends on it, you depend on it, or it simply would be awful (or worse!) if something happened to it, then you should develop some operating procedures that protect it. Protect it from natural disasters, human caused disasters, vandals, and the most likely of all disasters - the one that you cause,

You should::

1. Make regular backups of your production installation of DNN. That's a basic disaster recovery practice. Keep copies somewhere that's protected. The server that runs your website is not a good place to store those disaster recovery copies.

2. Make a special backup before you do an upgrade. If you do that, reverting from an unsuccessful backup should be a snap!

3. If possible, never do a live upgrade to a production system. Make a copy, upgrade it offline, test it, and use a copy of the the upgraded installation to upgrade the production installation. (I realize that there are cases where this isn't possible. In that case, follow rule #2 several times, and make multiple backup copies. Yes, I am that paranoid, and I have the experience to justify it.)

All that said, going from major version to major version should inspire caution. Read the release notes, read the forums, ask around ...

Now, back to your regularly scheduled programming ...