Goals:
- respond as quick as possible to mw releases i.e. invest the least time into getting a wbSuite release out after a mw release has been published => some sort of Continuos Deployment?
- allow building from main branches and understand how this can be automated in CI
Current Situation:
- each time that we have tackled a release we have run the pipeline against all the code changes that had happened over months. Doing that check every day, every week or even every 2 weeks will massively reduce the amount of code changes in Wikibase as well as the extensions. That would also reduce the probability of errors as well as the time we need to invest into fixing them.
- commit hashes of the extensions are checked and added manually. We want this to be easier/more automated.
- currently, we build our wikibase containers based on mediawiki docker containers, which are only released after the mediawiki release. So part of this ticket would also be to create our own mediawiki docker containers based on mediawiki main/master branch.
Open Questions: the discussion whether we want to keep up with the mw release cadence and how often we want to make releases in between can definitely come up here. (T340230)