Closed ericgaspar closed 9 months ago
!testme
Look good to me - but I guess we´d want to merge the postgres migration first, handle the bugs and fixes, and then look at the manifest v2 again?
!testme
!testme
!testme
To minimize the changes brought by the Postgres migration, would it be sensible to wait for the migration to be in production and debugged before merging another important change?
!testme
!testme
!testme
!testme
!testme
!testme
!testme
!testme
!testme
!testme
!testme
shall we merge to testing?
Seems good to me theoretically – but there still an upgrade test failing (upgrading from mattermost 7.3 to this version).
Also maybe we should add a test to check that upgrading from the current version (7.8.1) still works (although that will also be covered by real-life testing).
!testme
!testme
!testme
!testme
The migrations should be fixed.
Now there's just the issue of deleting the PG base after a failed MySQL migration, and we should be good.
!testme
(Btw, when merging this PR, we should squash the 235 commits into one: a numbers of temporary commits this large won't do any good to the git history)