I should probably add that every time I've tried to upgrade Mahara, I've hit the same problem: there's a mismatch between the documentation and the actual upgrade path.
"Upgrade to 1.10+ fails on Postgres <9.1" https://bugs.launchpad.net/mahara/+bug/1517658
- Docs said postgres version supported, but upgrade failed. In this case, a patch was provided by Catalyst and the upgrade proceeded.
"Upgrade to 17.04 fails on Postgres 8" https://bugs.launchpad.net/mahara/+bug/1700893
- Docs said postgres version supported, but upgrade failed. Postgres version actually was not supported.
"19.04 README says direct upgrade from 15.04.0 and later, but upgrade.php says must upgrade to 17.04.0 first" (This one.) https://bugs.launchpad.net/mahara/+bug/1830847
- Docs said direct upgrade, but intermediate step was required.
It could be worth adding a step in the release process to check these things off. People like me (or not like me) do upgrade planning based on the system requirements, so it matters that they're correct.
This is probably kind of obvious, but, after bumping into this three times, it seems worth a mention.
I should probably add that every time I've tried to upgrade Mahara, I've hit the same problem: there's a mismatch between the documentation and the actual upgrade path.
"Upgrade to 1.10+ fails on Postgres <9.1" /bugs.launchpad .net/mahara/ +bug/1517658
https:/
- Docs said postgres version supported, but upgrade failed. In this case, a patch was provided by Catalyst and the upgrade proceeded.
"Upgrade to 17.04 fails on Postgres 8" /bugs.launchpad .net/mahara/ +bug/1700893
https:/
- Docs said postgres version supported, but upgrade failed. Postgres version actually was not supported.
"19.04 README says direct upgrade from 15.04.0 and later, but upgrade.php says must upgrade to 17.04.0 first" (This one.) /bugs.launchpad .net/mahara/ +bug/1830847
https:/
- Docs said direct upgrade, but intermediate step was required.
It could be worth adding a step in the release process to check these things off. People like me (or not like me) do upgrade planning based on the system requirements, so it matters that they're correct.
This is probably kind of obvious, but, after bumping into this three times, it seems worth a mention.
Cheers,
Marcus