| daniel added a comment. |
@WMDE-leszek That is essentially it. This is a (potentially) breaking change for tools on labs. According to https://www.wikidata.org/wiki/Wikidata:Stable_Interface_Policy#Stable_Public_APIs, it should be announced four weeks before we deploy it. I think in this case, we can get away with stopping updates to the table earlier (so we can drop the code), but keeping the table around for a few weeks. I doubt there are many tools on labs that use this table, if any.
Generally, database updates defined to run on update.php are not run on the live cluster. We would put the update code on master, and file a ticket for the DB change to be applied to the cluster manually. In this case, we should make sure the table is only dropped four weeks after we announced the change.
As you can see, I did not fully think through the deployment process for this. Ideally, we would have announced earlier, or we had held back the change that dropped the code for updating the table. Oops... But I don't think it's a big deal. As I said, I doubt many scripts rely on this table. Shouldn't be too much of a problem to stop writing to it.
Cc: WMDE-leszek, Ladsgroup, Aklapper, hoo, gerritbot, Tobi_WMDE_SW, Zppix, daniel, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, Lewizho99, Maathavan, Izno, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
