Minor upgrade instructions (4.0.1 -> 4.0.3)

[setecastronomy]

In the latest admin manual there is nothing about minor upgrade (when only the last number increments).
Can I refer to the 3.3 admin manual where I can find a list of steps to follow for minor upgrades ?

I'm not very skilled with Linux, so the installation of Otrs 4.0.1 from sources took me lots of time and I performed it few days ago.
Now I would have to redo this activity again.
I guess I have to move 4.0.1 in /opt/otrs_old and install the new one in /opt/otrs. Do I have to launch any database script ?
I think the information about the database connection will be available to 4.0.3 after copying Config.pm from 4.0.1. Is it correct ?


Thanks
Filippo

[reneeb]

From http://otrs.github.io/doc/manual/admin/ ... ading.html

These instructions are for people upgrading OTRS from 3.3 to 4 or from a 4 to a later patchlevel release 4 and applies both for RPM and source code (tarball) upgrades.

If you are running a lower version of OTRS you have to follow the upgrade path to 3.3 first (1.1->1.2->1.3->2.0->2.1->2.2->2.3->2.4->3.0->3.1->3.2->3.3)! You need to perform a full upgrade to every version in between, including database changes and the upgrading perl script.

Please note that if you upgrade from OTRS 2.2 or earlier, you have to take an extra step.

Within a single minor version you can skip patch level releases if you want to upgrade. For instance you can upgrade directly from OTRS 4 patchlevel 2 to version 4 patchlevel 6. If you need to do such a "patch level upgrade", you should skip steps 6, 11, 13 and 14.

It is highly recommended to perform a test update on a separate testing machine first.