Last modified: 2014-03-04 13:32:35 UTC
I'm not quite sure when this is going to be a problem for production (hashar has already been through it with beta as they run master)
But what new extensions need branching? What versions do we need to use of them? What configuration updates are needed? Do we need to have version dependent requires?
In 1.22wmf7 we're still using the 1.22wmf6 branches. The same will be the case for wmf8 if no newer branches are created (as previously occurred)/the updates are documented/notified in both config and make-wmf-branch.
It might not be an issue till 1.22wmf9 or later...
I think the WikiData folks are planning on skipping cycles, ie: only update on the odd wmfXXs.
Otherwise, we could automatically create branches for it from either 1) the same branch point as the previous one or 2) an updated point based on a commit from the WikiData team.
What Greg says. We plan to skip cycles, and they might even be irregular. Actually I guess we should find a better way to handle this, but for now assume that we are only deploying every other week.
I have mailed Jeroen to get a confirmation. He adopted Composer to define dependencies after I played with it back in January. So one can see the dependencies on https://packagist.org/packages/wikibase/wikibase :
Jeroen confirmed by email the new dependency would be WikibaseDataModel (it is not in make-wmf-branch/default.conf ). It has 'master' and '0.4.x' branches and a 0.4 tag.
Indeed, the only relevant new repo is WikibaseDataModel. When running a version of Wikibase from before WikibaseDataModel was split off, then just use Wikibase. When running a version of it after the split was made, then WikibaseDataModel needs to be loaded as well.
The bug in beta was https://bugzilla.wikimedia.org/show_bug.cgi?id=49594 "" Class 'Wikibase\EntityId' not found on beta cluster""
Been fixed inside Wikibase somehow :)
[replacing wikidata keyword by adding CC - see bug 56417]
We're deploying from one repository now. I consider this fixed.