As advertised on the Integration, exposed forum, the code freeze for Moodle 2.6 began yesterday. This means that we will only be accepting bug fixes into core for the next month or so, until the release of Moodle 2.6. 
As is often the case, we've got a large amount of last minute changes landing in the last week, so your patience is requested while we integrate these changes. Over the next week we will be working our way through the backlog of submitted issues and aim to start 2.6 QA after this is completed.
If you have submitted new changes during this release:
- Please help us ensure we have QA tests for new features, especially those flagged with qa_test_required (please add that label to your issue if it needs a qa test but hasn't been labeled). Behat acceptance tests will especially be appreciated.
- Pay particular attention to your issues flagged dev_docs_required or docs_required.
- Start filling out Moodle 2.6 Release Notes with the fantastic features you've added. (Especially those flagged ui_change).
- Ensure any API Changes are correctly documented.
If you are interested in the developer changes in this release, look at the various upgrade.txt files. There have been a large number of deprecations this release, but please don't panic too much as many of these are deprecations from Moodle 1.9 which have be properly deprecated to ensure they throw developer warnings.
Dan and the Integration team
 All rules are made to be broken, if necessary