The M2C code has been rolled back in the Gerrit branch m2c-rollback. This should replace the current master branch and the M2C code will be merged later. The current master branch should be moved to another branch until the merge, called something like m2c.
Description
Description
Related Objects
Related Objects
- Mentioned Here
- T231751: Depicts selector too big
T295486: API routes do not return appropriate response codes
T304090: Campaigns and contributions are added with no users
T312068: Update code to use recent release of WTForms
T312178: Add Commons base file path to config file
T312179: Campaign stats file directory occurs severally in campaign routes
T315668: Submit reviews back to MachineVision service
T316197: Split CSS file by page
T318843: Denylist for depict items that shouldn't be used
T324103: ISA tool uses third party cdn
T325735: Cannot Download all stats (CSV)
T325791: Cannot find a specific string to translate
T327071: Fix user campaign relationship
T327618: Remove unused packages from application blueprints
T334418: User setting validation generates Bad request
T337291: Server requests for rollback on failing operation
Event Timeline
Comment Actions
@siebrand Will the syncing with translatewiki.net be affected by these changes?
The existing translations (in master today) will be migrated to the new m2c branch so they won't be lost but I'm unsure how this might affect the message pages on translatewiki.net now and in the future when the m2c branch is merged back into master.
Comment Actions
@NavinoEvans, @Eugene233, I poked around a bit in a different repo (where I have +2) and I think the way to make the switch is like this:
- Create a new branch for m2c with "Initial Revision" = master.
- Delete the master branch.
- Create a new branch called master with "Initial Revision" = m2c-rollback.
- Delete the branch m2c-rollback, once everything looks good.
I don't know what happens with the patches after that, but it's likely that at least some patches will have to be moved so they belong to the correct branch, depending on if they are for M2C or not. This can be done in the Gerrit web interface via the "three dot menu" at the top, but only if you own the patch or if you have +2 for the repo (I think).
Comment Actions
@Sebastian_Berlin-WMSE Sure some patches would have to be moved. I managed to identify the existing patches(in review) which may have to be moved once this change is made.