==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):  1.0.0 to 1.1.0
- Deployed with iRedMail Easy or the downloadable installer? downloadable installer
- Linux/BSD distribution name and version: Ubuntu Server 18.04.5 LTS
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): NginX
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

I'm in the process of upgrading an iRedMail installation I inherited.

Linux server and all packages on it are fully upgraded, iRedMail is still on version 1.0. with some work done upgrading to 1.1

I have some qualms after reading the documentation re upgrading in "https://docs.iredmail.org/iredmail.releases.html"

--------------
In all singular upgrade pages the instructions are to migrate to the "Latest" version of the main parts of the server (iRedAPD, iRedAdmin, mlmmjadmin , roundcube etc..), but the ones referenced are the latest at the moment a specific guide was written ( for example roundcube 1.4.3 at the https://docs.iredmail.org/upgrade.iredmail.1.1-1.2.html guide.

So, do we update at the Current latest packages for these programs while updating older versions?

For example: While Updating iRedMail 1.1 to 1.2 should I upgrade to Roundcube 1.4.3 or the now (26/10/20) current 1.4.8?

if the second option is valid, do we simply ignore said component in subsequent upgrades ??
( in our case 1.1 > 1.2 >> 1.2.1 >> 1.3 >> 1.3.1 )

I already upgraded iRedAPD from 3.3 to 4.5 and everything seems to be working great but I'm not sure i did the right thing.

--------------
Can we possibly skip the "minor version" upgrades ( for example 1.2.1) and go straight from point release to point release? ( 1.2 > 1.3). Guessing not from the wording, just thought to ask.

--------------
if I take a backup ( DB using the iRedMail-[VERSION]/tools/backup_mysql.sh script in my case), and the update fails for some reason, is it safe to restore the DB to a newly setup "OLD version" server while ironing out problems in the "NEW version" ?
Asking because I'm worried I might get stuck updating.