[SOLVED] Upgrade from 3.1.0.b2 to 3.1.0.b3

[dolfiz]

Hi all,

according to this post (viewtopic.php?f=62&t=12987) I would like to upgrade a 3.1.0.b2 version of OTRS to 3.1.0.b3 (I'm experiencing the same problem as the topic linked and I need to solve the problem with the minimum impact on the webapp).

Where can I find the 3.1.0.b3 version? Or as an alternative the RC one? I tried on ftp.otrs.org but there is a jump from 3.0.9 to 3.1.1. Should I have to use the 3.1.1?

As always, thank you for your precious help.
Luca

[jojo]

which version you are running now?
If you want to stay in the minor releae use the latest 3.0.x which is 3.0.22.
if you wan't to upgrade to the latest release this is 3.3.4 (which needs to upgrade to 3.1.latest and 3.2.latest first)

[dolfiz]

which version you are running now?
If you want to stay in the minor releae use the latest 3.0.x which is 3.0.22.
if you wan't to upgrade to the latest release this is 3.3.4 (which needs to upgrade to 3.1.latest and 3.2.latest first)

Thank you jojo for your reply.

Currently I am on 3.1.0.beta2 and my only concern is to fix the problem regarding email fetching (as the link viewtopic.php?f=62&t=12987).

My wish is to apply nothing but the FIX, so I'm not targeting earlier versions. This to soften impacts on a system that I did not build and whose customizations I'm not aware of (who knows if the previous devs changed files from the OTRS core?! I'm scared about it!). The problem is that I cannot find the 3.1.0.beta3 version, so I guess I need to download the first next stable that, I think, is the 3.1.1, right? I was wondering why the repository does not list all the versions (where is the 3.1.0?).

[jojo]

I can see the versions on the ftp server. Always use the latest version of the release

[dolfiz]

I can see the versions on the ftp server. Always use the latest version of the release

So, are you suggesting the last of the 3.1.* series? The 3.1.19?

[jojo]

as I wrote above. I you wan't to upgrade use the latest version 3.3.4

[dolfiz]

as I wrote above. I you wan't to upgrade use the latest version 3.3.4

There are many reason to upgrade to the latest version, I know, but simply this is not the case. As far as I know there are so many differences between 3.1 and 3.3. I really don't want to upgrade the system, I just want to apply the FIX for the problem. There's no point to make changes to a system that is used from months. The request is to apply a FIX, not to upgrade a whole system. So, If I need to upgrade because it's the only way to apply the FIX, let the upgrade be the simplest, trying to avoid also the smallest change on the system the users are accostumed to.

[crythias]

At least 3.1.latest, then. Early beta releases do not have patches and security fixes you will need as well. Pay attention to the release notes/Changes.md

[dolfiz]

At least 3.1.latest, then. Early beta releases do not have patches and security fixes you will need as well. Pay attention to the release notes/Changes.md

Perfect, so I'll go with the 3.1.19, backing-up everything and checking release notes and best practice for upgrading.

I really don't know why they pushed a beta realease on production environment. Not a wise decision

Thank you for your suggestions,
Luca

[crythias]

You are referencing a 2011 thread for a basis to make a change to your production environment.

[dolfiz]

You are referencing a 2011 thread for a basis to make a change to your production environment.

Do you think that this is not the proper way to handle the problem? Using an old release I think it's normal to find useful info on old threads, no?

I'm aware of the advantages that an upgrade to the last version could offer, but, as I've said, a major upgrade it's not an option. Although often I'm not in accord with my clients decision, in this scenario I think is resonable to request that the system changes less possible.

By the way, I've seen OTRS 2.4 on production environment working good and clients that don't want to upgrade it 'cause they don't see the point to do that, they were already satisfied :/ How can we say? It's ugly and with less functionalities, but 2.4 still works and the client is the decision maker

[crythias]

Do you think that this is not the proper way to handle the problem?

I do not in this case.

My specific point is that the effort to upgrade to 3.1.0b3 is roughly identical to upgrading to 3.1.latest.You will need to patch the database because you're upgrading from beta2.

I really don't know why they pushed a beta realease on production environment.

I may have misread the intended noun of "they" ... I assumed you meant OTRS, but you could have meant your client.

[dolfiz]

My specific point is that the effort to upgrade to 3.1.0b3 is roughly identical to upgrading to 3.1.latest.You will need to patch the database because you're upgrading from beta2

You are right, I was checking the upgrading process and unfortunately I need to patch the db. I think that jumping to the latest version of the 3.1.* series is a good tradeoff: not massive changes but many useful fixes. I would like to underline that the problem is not the effort spent on the upgrading process, but the need to minimize changes on the webapp in order to avoid surprises for the user accostumed to a slightly different interface.

I really don't know why they pushed a beta realease on production environment.

I may have misread the intended noun of "they" ... I assumed you meant OTRS, but you could have meant your client.

Sorry, it was ambiguous: I was talking about my client. Actually it seems to me that they used that beta release in order to benefit from the new Dynamic Field functionality that, if I remember well, has been released on 3.1 final.

[crythias]

(BTW, I agree with you in spirit in keeping the 3.x level for conformity reasons. I'm on 3.0 production for a similar reason.).