|· · ·|
|Open||None||T174043 Deploy Multi-Content Revisions|
|Open||None||T174022 Implement multi-content revisions|
|Open||None||T198492 Drop rev_text_id and ar_text_id when running update.php|
|Open||None||T198557 Remove support for legacy pre-MCR schema|
|Open||BPirkle||T198341 Remove all references to the rev_text_id and ar_text_id fields|
|· · ·|
Well, SCHEMA_COMPAT_WRITE_OLD is effectively the default now.
Dropping these fields basically means only SCHEMA_COMPAT_WRITE_NEW | SCHEMA_COMPAT_READ_NEW is supported. So it can only be done after migration is complete.
I was planning to create a few more tickets to track the steps towards that point. Will do that later, running out of battery...
It's just a bit scary when that's triggered by update.php - if something goes wrong with the migration script you could lose all content.
When HitCounter was removed from core the update just deleted all stored data, which understandably made people very unhappy. We should not do something like that again, even by accident.