Incremental update (3.5.3 -> 3.5.4)

Incremental update (3.5.3 -> 3.5.4)

by Lee Phillips -
Number of replies: 3

Hello everyone,

   I would like to ask whether an incremental update (3.5.3 to 3.5.4) requires the same process as upgrading (e.g. 3.4 to 3.5, or 3.5 to 3.6).

   I just took over as the admin of my company's customer-facing Moodle, but unfortunately neither I nor any of my colleagues has any experience of installing or upgrading Moodle.

   Our current version is 3.5.3. We want to avoid upgrading until the next LTS version comes out, but it seems sensible to take the incremental update to 3.5.4.

   There is plenty advice for upgrading from a previous version, but nowhere in the documentation (AFAIK) is any distinction made between such upgrades and the incremental, bug-fix updates within one version.

Is the process exactly the same? Is any part of the process easier or unnecessary (e.g. can I expect the plugins to work without needing their own upgrades?)

   Thanks very much for your time in assisting a novice!

Lee

Average of ratings: -
In reply to Lee Phillips

Re: Incremental update (3.5.3 -> 3.5.4)

by Ken Task -
Picture of Particularly helpful Moodlers

Sticking with a long term support version is a good idea.
Bug fixes for general core bugs in 3.5.x will end 13 May 2019 (12 months).
Bug fixes for security issues in 3.5.x will end 10 May 2021 (36 months).

Official docs are here:
https://docs.moodle.org/35/en/Upgrading
Process is the same for an update or an upgrade - update being an incremental upgrade
like 3.5.x to 3.5.highest at the time.

Depending factors consider using Git for updates or upgrades.
https://docs.moodle.org/35/en/Git_for_Administrators
One major factor ... customizations of core code and addons/plugins.

And for future ... check the environment of your current system.
Admin -. Server -> Environment.  Update Component.
Then look at environment requirements for 3.6 and beyond.
Mention this now cause later its sorta outta sight, thus outta mind.
Tne Notifications screen where one sees the growing number
of updates isn't linked to the Environment Check.
 
Even a minor update might be best done in a clone sandbox server first.
And before pulling the trigger on production server, do a full site backup ...
code + DB SQL dump + data directory.  You won't ever regret taking the time to do a full site backup! smile

'spirit of sharing', Ken



Average of ratings: Useful (1)
In reply to Ken Task

Re: Incremental update (3.5.3 -> 3.5.4)

by Lee Phillips -

That is brilliant, thank you for the advice Ken! smile

I will follow the usual process to update to 3.5.4, and try to get a clone server so I don't have to take risks with the production server.

Lee

Average of ratings: -
In reply to Lee Phillips

Re: Incremental update (3.5.3 -> 3.5.4)

by Ken Task -
Picture of Particularly helpful Moodlers

Well ... thanks ... but can't claim 'brilliance' ... what I've described has always been the recommendation as far back as I can re-call ... clone of production site to a sandbox and test updates/upgrades/other plugins there first before working on production site.

Worth the effort, IMHO! ;)

'spirit of sharing', Ken


Average of ratings: -