Topic on Talk:Requests for comment/Multi-Content Revisions

Was deprecated in 1.31, hard deprecated in 1.35, and removed in 1.37

Now that this has landed, what is the plan for the Revision class? The release notes for MW 1.31 say this class is now deprecated, however this page indicates that it will remain as a simple wrapper for the most common use-case; accessing the main slot (and, commonly, the main slot of the current revision, e.g. instantiation vianewFromTitle()).

Which is it? Deprecated or not?

If it is the former (the class is deprecated and is destined to be removed) we need some migration documentation set up. I would be happy to create the template for this, but would require some more knowledgeable people to populate the details.

It's still being worked upon. I don't think there will be a settled status for at least another year of development, sorry.

Thanks for the reply. Does that mean that it hasn't been decided whether Revision will be removed yet, and it may end up being kept? Or is it that it will definitely be removed in due course but we don't yet know the detail about what the new code will look like or when that will be?

The release notes for 1.31 say it has been deprecated, but it sounds like this is premature and should perhaps be removed from the release notes, as these are what guide us extension developers about what things we need to fix in order to remain compatible. If there is no change to how the class should be used, nor any recommended alternative, then surely it hasn't been deprecated yet?

It took a long time, but finally someone has written some migration notes for switching to the new methodology: Manual:Revision.php/Migration

Yes, thank you to @DannyS712.