version = 2021052500 release version
requires= 2021052500 same than version
Why 20210525? (25th May 2021) ?
Because master is going to be Moodle 4.0, to be released
on November 2021. And, until then, we are going to have
a couple of "intermediate" releases:
- Moodle 3.10 to be released 9th November 2020. (2020110900)
This version will be using versions from today to 2020110900
(once it's released the YYYYMMDD part stops advancing).
- Moodle 3.11 to be released 10th May 2021. (2021051000)
This version will be using versions from 3.10 release to 2021051000
(once it's released the YYYYMMDD part stops advancing).
That means that all versions from today to 2021051000 are going
to be used by those 2 "intermediate" releases (3.10 and 3.11).
And we cannot use them in master, because it's forbidden to have
any overlapping of versions between branches (or different upgrade
paths will fail).
So, get that 2021051000, let's add it a couple of weeks to cover
the on-sync period (or a 2 weeks delay max!) and, the first version
that master can "own" in exclusive (without any overlap) is, exactly,
25th May 2021, hence our 20210525.
Significant string changes:
* moodleorghubname,core_admin and
sitemustberegistered,message_airnotifier - 'Moodle.net' changed to
'Moodle'
* registration_help,core_admin and registermoochtips,core_hub - removed
erroneous 'access to Moodle.net our course sharing platform'
* trackingtype_help,mod_forum and formnotavailable,core_grading and
showgrades_help,core and rolewarning_help,core_rating -
'Administration block' changed to 'Actions menu or admin block',
'navigation block' changed to 'navigation drawer or block'
The new recordset support for Postgres requires transactions and
will cause errors if recordsets are not closed correctly. This
commit fixes problems that were identified during unit tests, and
via some basic code analysis, across all core code. Most of these
are incorrect usage of recordset (forgetting to close them).
version = planned 2015051100 release version
requires= current 2015050500 rc1 version
Note: On purpose, the course format social wrong version (2015102100)
has been kept unmodified. Looking forward a solution right now.
Why? Because this tool does not support contexts, allows data modifications and is intended only for admins. It is still linked from admin reports for now, we will move it elsewhere once we know where to add general new reports.
AMOS BEGIN
MOV [pluginname,report_spamcleaner],[pluginname,tool_spamcleaner]
MOV [spamauto,report_spamcleaner],[spamauto,tool_spamcleaner]
MOV [spamcannotdelete,report_spamcleaner],[spamcannotdelete,tool_spamcleaner]
MOV [spamcannotfinduser,report_spamcleaner],[spamcannotfinduser,tool_spamcleaner]
MOV [spamcleanerintro,report_spamcleaner],[spamcleanerintro,tool_spamcleaner]
MOV [spamdeleteall,report_spamcleaner],[spamdeleteall,tool_spamcleaner]
MOV [spamdeleteallconfirm,report_spamcleaner],[spamdeleteallconfirm,tool_spamcleaner]
MOV [spamdeleteconfirm,report_spamcleaner],[spamdeleteconfirm,tool_spamcleaner]
MOV [spamdesc,report_spamcleaner],[spamdesc,tool_spamcleaner]
MOV [spameg,report_spamcleaner],[spameg,tool_spamcleaner]
MOV [spamfromblog,report_spamcleaner],[spamfromblog,tool_spamcleaner]
MOV [spaminvalidresult,report_spamcleaner],[spaminvalidresult,tool_spamcleaner]
MOV [spamoperation,report_spamcleaner],[spamoperation,tool_spamcleaner]
MOV [spamresult,report_spamcleaner],[spamresult,tool_spamcleaner]
MOV [spamsearch,report_spamcleaner],[spamsearch,tool_spamcleaner]
AMOS END
