- 09 Nov, 2021 1 commit
-
-
Adrian Greeve authored
Co-authored-by:
Sujith Haridasan <sujith@moodle.com>
-
- 12 May, 2021 1 commit
-
-
Eloy Lafuente authored
It seems that the new phpcs3 checker is now controlling those line comments that previously were ignored. This commit just looks for all the cases and bulk-add them when needed. The bash script (mac) used to add all them is: while read -r line; do arr=(${line//:/ }) if [[ -n ${arr[0]} ]] && [[ -n ${arr[1]} ]]; then echo " file ${arr[0]}, line ${arr[1]}" sed -i "${arr[1]}s/\$/\./" ${arr[0]} fi done < <(find . -name version.php | xargs ag --nomultiline '>(version|requires) *=.*//.*[^;\.]$')
-
- 28 Sep, 2020 1 commit
-
-
Nathan Nguyen authored
-
- 18 Aug, 2020 1 commit
-
-
Eloy Lafuente authored
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.
-
- 17 Aug, 2020 1 commit
-
-
Eloy Lafuente authored
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 mater, 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.
-
- 09 Jun, 2020 1 commit
-
-
Eloy Lafuente authored
version = 2020061500 release version requires= 2020060900 current rc1 (week7roll1) version
-
- 13 Nov, 2019 1 commit
-
-
Eloy Lafuente authored
version = 2019111800 release version requires= 2019111200 current beta (week7roll1) version
-
- 13 May, 2019 1 commit
-
-
Eloy Lafuente authored
version = 2019052000 release version requires= 2019051100 current beta (week6roll2) version
-
- 30 Nov, 2018 1 commit
-
-
Eloy Lafuente authored
version = 2018120300 release version requires= 2018112800 current rc2 (week7roll1) version
-
- 09 May, 2018 1 commit
-
-
Eloy Lafuente authored
version = 2018051400 release version requires= 2018050800 current beta+ (week4roll1) version
-
- 10 Nov, 2017 1 commit
-
-
Eloy Lafuente authored
version = 2017111300 release version requires= 2017110800 current rc2 version
-
- 09 May, 2017 1 commit
-
-
Eloy Lafuente authored
version = 2017051500 release version requires= 2017050500 current rc1 version
-
- 21 Apr, 2017 1 commit
-
-
- 30 Nov, 2016 1 commit
-
-
Eloy Lafuente authored
version = 2016120500 release version requires= 2016112900 current rc4 version
-
- 19 May, 2016 1 commit
-
-
Eloy Lafuente authored
version = 2016052300 release version requires= 2016051900 current rc1 version
-
- 04 Mar, 2016 1 commit
-
-
Juan Leyva authored
-
- 10 Nov, 2015 1 commit
-
-
Eloy Lafuente authored
version = planned 2015111600 release version requires= current 2015111000 rc3 version
-
- 21 Sep, 2015 1 commit
-
-
Juan Leyva authored
-
- 04 Sep, 2015 1 commit
-
-
Juan Leyva authored
-
- 05 May, 2015 1 commit
-
-
Eloy Lafuente authored
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.
-
- 05 Nov, 2014 1 commit
-
-
Eloy Lafuente authored
This bumps all versions to planned 2.8 release (2014111000) version and all the dependencies to current 2.8rc1 (2014110400)
-
- 29 Oct, 2014 1 commit
-
-
David Balch authored
Based on a patch by Matthew Cannings, this replaces Book's previous/next arrow image links with a choice of: no links, image links, or chapter title text links.
-
- 09 May, 2014 1 commit
-
-
Eloy Lafuente authored
This bumps all versions to planned 2.7 release (2014051200) version and all the dependencies to current 2.7rc2 (2014050800)
-
- 29 Jan, 2014 1 commit
-
-
Conflicts: mod/quiz/version.php
-
- 05 Nov, 2013 1 commit
-
-
Eloy Lafuente authored
-
- 02 May, 2013 1 commit
-
-
Eloy Lafuente authored
-
- 30 Nov, 2012 1 commit
-
-
Eloy Lafuente authored
(versions, requires and dependencies)
-
- 21 Oct, 2012 1 commit
-
-
Eloy Lafuente authored
This commit replays, conditionally, all the upgrade steps from MOODLE_19_STABLE to MOODLE_23_STABLE in the mod_book activity. That guarentees that any site using the mod_book before landing to core, no matter if it was the latest or an outdated one will upgrade perfectly to the expected current version. As a general rule, everytime one contrib plugin lands to core, its complete upgrade code must be kept, at least until the core version that introduced it, is out completely from the upgrade requirement conditions. In this case, with the missing upgrade code being added to 2.4, it will be safe to delete the upgrade steps once 2.5 (or upwards) become a requirement. Never always.
-
- 11 Oct, 2012 1 commit
-
-
Ankit Agarwal authored
-
- 07 Sep, 2012 1 commit
-
-
Ankit Agarwal authored
-
- 16 Aug, 2012 1 commit
-
-
Ankit Agarwal authored
-
- 18 Jun, 2012 1 commit
-
-
Eloy Lafuente authored
-
- 13 Jun, 2012 1 commit
-
-
Rossiani Wijaya authored
-
- 27 May, 2012 1 commit
-
-
Eloy Lafuente authored
- Replace numberingoptions_help by numberingoptions_desc. - Delete the faq code and related styles. - Bump version to force lang/style refresh.
-
- 21 May, 2012 3 commits
-
-
Eloy Lafuente authored
-
Eloy Lafuente authored
-
Eloy Lafuente authored
-