Three niggles I'd classify as bug reports:

1. The documentation for the 3.11 upgrade install (/docs/mtupgrade.html) does not cover the case for upgrading from 3.1. While the release notes hint that the mt-upgrade scripts have been tweaked to handle Berkeley DB, the wording is unclear and/or imprecise, and it's not obvious if we should now run those scripts. Nor if it's even safe to do so.

2. For newcomers and casual users, 'Run mt-upgrade31.cgi' (/docs/mtupgrade.html) may be unclear without consulting additional documentation. The introductory paragraph for 'Running Upgrade Scripts' should be explicit on how one goes about doing this.

3. Finding the relevant documentation is harder than it could be. At the very least, an index.html in /docs/ would reduce the clutter through which one is sifting.

Bumping this, since the documentation does not appear to have changed with v3.12.

As a result, docs/mtupgrade.html now does not provide instructions on upgrading from to v3.12 from v3.1 or v3.11. The most recent version mentioned is v3.01D.

My apologies if I'm being prissy about this, but it seems to me that reviewing the upgrade documentation should be in the pre-release checklist; at the very least, the documentation should give general advice on point updates of the v3.11 and v3.12 kinds.

As with previous versions, you do not need to run any upgrade scripts for 3.11 --> 3.12

The only times upgrade scripts are to be run are the situations listed in mtupgrade.html