A few days ago, latest releases included MOODLE_401_STABLE and MOODLE_402_STABLE with a comment which I think recommended these versions for production.
Maybe I am having a senior moment and on the wrong page but I can't find them.
https://download.moodle.org/releases/latest/ vs https://download.moodle.org/releases/supported/ vs https://download.moodle.org/releases/security/. One of the tricks HQ uses to push the users to the latest and shiniest.
https://download.moodle.org/releases/latest/ has MOODLE_4022
https://download.moodle.org/releases/supported/ has MOODLE_4015
https://download.moodle.org/releases/security/ has MOODLE_40010 and 3.x versions
Last week there was a choice - now we don't have one. Are we being directed away from the stable version? I thought stable was best for LTS.
MOODLE_4022 does not have any information on end of security updates. Is that not important now when selecting your release?
If you mean the Git repo, there is only one: git://git.moodle.org/moodle.git. MOODLE_401_STABLE is a branch. Just follow https://docs.moodle.org/401/en/Git_for_Administrators#Obtaining_the_code_from_Git and you'll get the 4.1.current.
I am already using the stable versions in git - but the removal of these versions from the list of releases made me wonder if I am getting the wrong versions.
So is MOODLE_401_STABLE only for those who use git? I can't see a download link.
A previous comment of yours pointed out 4.1 can be a better choice than 4.2, something I had never considered. But where has the end of life advice gone?
- Yes, the "keyword" (branch) MOODLE_401_STABLE exists only in the Git repo. The equivalent direct download is under https://download.moodle.org/releases/supported/. If you download today, you will get 4.1.5 which is the 4.1.current. The Git repo and the direct code download are not (directly) coupled together.
Note: Anybody can branch his Git repo and call it MOODLE_401_STABLE. In fact some additional plug-ins name their branches exactly as the Moodle core.
- Moodle 4.1 LTS destined to live longer than 4.2: Can be seen in https://moodledev.io/general/releases.
P.S. I suggest, we always write '3.9 LTS', '4.1 LTS'.
I can follow it now. The download page assumes the user keeps going back and downloads 4022, 4023 and so on. Meanwhile the git page - one for each release , differing only by 3 characters - needs to be consulted to find the stable version. I think you call that "bag and baggage". And if you want to know when your newly installed Moodle is no longer supported, you go to the Moodle developers section because that is presumably developer area knowledge which Moodle users don't have to worry about. And you have to know MOODLE_401 is actually Moodle 4.1 because there is no link between git branch and the release.
I liked the old way where stable releases were on the download section with end dates. Create one generic git page and expect people to be able to substitute an updated release number.
You are not the first to fell in to this: Ref. https://moodle.org/mod/forum/discuss.php?d=449561#p1806794.
Hi
I didn't read this part in my earlier reply:
> The download page assumes the user keeps going back and downloads 4022, 4023 and so on.
At any given time, there is only one point release on those download pages. As of now https://download.moodle.org/releases/latest/ gives you moodle-4.2.2.tgz, which is obviously Moodle 4.2.2, released 14 August 2023. I think, I never get Moodle from there, it stays there until the next point release 4.2.3 arrives in 2 months. The https://download.moodle.org/releases/latest/ says something about MOODLE_4022. Never seen that tag anywhere. In Git jargon it is always the "head" of the branch MOODLE_402_STABLE the user is interested in - which travels through 4.2.0 > 4.2.1 > 4.2.2 >... with time. To be certain, always read the version.php file in the Moodle code directory.
> Meanwhile the git page - one for each release , differing only by 3 characters - needs to be consulted to find the stable version.
Not true. This is the magic of Git. When you do 'git clone git://git.moodle.org/moodle.git now you'll get the whole history, every commit and the developer who submitted that since Moodle 1.3, 2003(?)
That is why the code tar.gz is only 63 MB and the Git repo is 842 MB. You do the 'clone' above once and from within you can jump to any major release starting from 1.3 by following Git_for_Administrators#Upgrading_to_a_newer_major_release. Not only that, given Git experience, you can jump to any point release since then or even march every commit since then. The only thing you can't do is to march into the future!
I didn't read this part in my earlier reply:
> The download page assumes the user keeps going back and downloads 4022, 4023 and so on.
At any given time, there is only one point release on those download pages. As of now https://download.moodle.org/releases/latest/ gives you moodle-4.2.2.tgz, which is obviously Moodle 4.2.2, released 14 August 2023. I think, I never get Moodle from there, it stays there until the next point release 4.2.3 arrives in 2 months. The https://download.moodle.org/releases/latest/ says something about MOODLE_4022. Never seen that tag anywhere. In Git jargon it is always the "head" of the branch MOODLE_402_STABLE the user is interested in - which travels through 4.2.0 > 4.2.1 > 4.2.2 >... with time. To be certain, always read the version.php file in the Moodle code directory.
> Meanwhile the git page - one for each release , differing only by 3 characters - needs to be consulted to find the stable version.
Not true. This is the magic of Git. When you do 'git clone git://git.moodle.org/moodle.git now you'll get the whole history, every commit and the developer who submitted that since Moodle 1.3, 2003(?)
That is why the code tar.gz is only 63 MB and the Git repo is 842 MB. You do the 'clone' above once and from within you can jump to any major release starting from 1.3 by following Git_for_Administrators#Upgrading_to_a_newer_major_release. Not only that, given Git experience, you can jump to any point release since then or even march every commit since then. The only thing you can't do is to march into the future!
> I think you call that "bag and baggage".
No. I used that to mean the doubling of Moodle Docs every 6 months.
P.S. We repeatedly have long discussions and explanations on what MOODLE_401_STABLE is. The oldies here are used to the "running length" counting, 30 (3.0), 31, 32, 33, 39, 310 (3.10), 311, 41, 42, .. which I call the techy way. Then there there is the "fixed length" counting, 300 (3.0), 301 (3.1), 302 (3.2), ... which is more verbose, bureaucratic. ("Three-zero-one, Three-zero-two, ..) I believe the Git commiter changed between 3.x and 4.x, from a techy to a bureaucrat.