I'm setting up MW 1.22 + VE for a client. To get a usable VE, I had find a working date (from the time REL1_22 was created on core branch) and use that code.
It would be good to have this branched so that there is a consistent bit of code to use.
Version: unspecified
Severity: normal
The REL1_22 branch for VE is created (currently pointing to 43e96d79271b5247668c28f90de18a2fd84a4d11) – see https://git.wikimedia.org/log/mediawiki%2Fextensions%2FVisualEditor/refs%2Fheads%2FREL1_22 – unless I'm missing something?
Note that VE-core isn't branched yet, as it's not yet being looked at by third parties outside of the MW context…
sorry, my bad. I meant parsoid. I went back to the version I got from
git checkout `git rev-list -n 1 --before="2013-12-17 13:37" master`
The Parsoid extension is already branched on MW releases. However, Parsoid itself isn't constrained by that cycle. We often push several deploys in the interim.
This is fine if I can use any future Parsoid with the Parsoid extension and MediaWiki branched at 1.24 or 1.23. Is that the case?
Yes, it should be. Parsoid produces a spec compliant output, so future releases are constrained by that contract.