On Wed, 2 Aug 2023 at 10:37, Kristian Nielsen via developers <developers@lists.mariadb.org> wrote: > Sergei Golubchik via developers <developers@lists.mariadb.org> writes: > > > There's a compromise approach - mariadb-upgrade is required (and thus > > downgrade does not work) between major versions, but mariadb-upgrade is > > not needed (and downgrade works) between minor versions. > > I agree with this approach.
Seems most people agree on this and it is also aligned with what https://mariadb.com/kb/en/downgrading-between-major-versions-of-mariadb/ states. Thus we should work towards architecting systemd scripts and other startup scripts to *not* run mariadb-upgrade automatically and restrict that only to major version upgrades. We need to stop running mariadb-upgrade both for users and in CI, so that users actually can benefit from this policy and that CI can detect if it is broken. Any change that requires mariadb-upgrade to run on a X.Y.n minor release should be treated as a bug, and MTR tests that call upgrade_from/test_upgrade.sh on minor upgrades should be adjusted to not run the upgrade at all. Still, having a future 11.X mariadbd run the upgrade automatically if it detects that there has been a major version upgrade would help simplify packaging/service scripts and prevent users from running into issues that arise if mariadb-upgrade was omitted after a major version upgrade. _______________________________________________ developers mailing list -- developers@lists.mariadb.org To unsubscribe send an email to developers-le...@lists.mariadb.org
