These are a set of common questions, which should be somewhere else, but I am too lazy to find the right place for them and frequently have to answer them. --Dan Poltawski 11:14, 12 June 2013 (WST)
Why do we not set the master version in the tracker fix version for bugs fixed in multiple branches
When an issue is fixed in the stable branches AND masters, we do not set the 'master version' in the list of fix versions. e.g. At the time of writing the master version is 2.6, and we support 2.5.x & 2.4.x. When we fix a bug in all 3 branches, we only set the fix versions as 2.5.1 and 2.4.3.
As we automatically build release notes based on tracker issues, so this is done so that people looking at the release notes for 2.6 upgrading from 2.5.4 don't see all the issues they've had fixed for months (from the 2.5.x point releases).
Related discussions
Lang pack download failed with 'HTTP response code: HTTP/1.1 404 Not Found' after new release
After we branch for a new release, Moodle will try and download the new version of langpacks, however for a while development is on-sync and no new language string differences will be introduced between the two branches. During this period, AMOS is not branched and so Moodle will fail to download new language packs.
This is expected and it will be resolved once AMOS is opened up for new changes in the new version.
Related discussions
- MDL-34028
- Chatlogs May 2013
- Chatlogs May 2013
- Chatlogs December 2012
- Chatlogs December 2012
- Chatlogs July 2012
Mark asks 'Do I have to run phpunit tests, aren't they run automatically?'
Yes.
Phpunit tests are currently running on the integration server automatically on every commit. However, at this time, it is only on a single (linux) environment with mysql. Work is in progress to run these tests automatically on a disparate sets of environments we support each day.
