moodle/repository/filesystem
Eloy Lafuente (stronk7) fbb0767536 MDL-69475 versions: bump all versions and requires in master
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.
2020-08-18 00:47:15 +02:00
..
classes MDL-64882 repository: Whitespace fix and version bump 2019-03-07 10:49:59 +08:00
db MDL-64882 repository_filesystem: convert cron to scheduled task 2019-03-01 11:12:46 +08:00
lang/en MDL-65397 lang: Import fixed English strings (en_fix) 2019-04-29 11:46:26 +02:00
pix MDL-50175 graphics: Optimized PNG images with optipng 2016-02-25 11:56:37 +00:00
tests/generator MDL-41580 SCORM: allow imsmanifest.xml to be used in file system repos 2013-09-24 12:08:38 +12:00
lib.php MDL-64882 repository_filesystem: deprecate legacy cron function 2019-03-01 11:12:55 +08:00
version.php MDL-69475 versions: bump all versions and requires in master 2020-08-18 00:47:15 +02:00