Need a strategy for updating ~70 plugins from 2.3.1 to 3.3.0

Added by Alexander Tkachev over 8 years ago

Our team is faced with massive upgrade from redmine 2.3.1 to 3.3.0. The problem is that we have ~70 plugins with many overrided views, alias_method_chains, decompositions of original redmine methods and such.

How would you do this? Is it better to migrate in steps? For example from 2.3.1 to 2.6.10, and than to 3.3.0? Or may be with narrower steps from point to point release?

How do I know what redmine releases introduce more changes than the others? I guess there are many differences between 2.x and 3.x, but what about minor versions? May be with this information it will be possible to calculate maximum upgrade step with minimal efforts.

Is there some tools which would help us to migrate? For example I wrote script that merges overrided views in plugins with updated views from upgraded redmine release.

Replies (2)

RE: Need a strategy for updating ~70 plugins from 2.3.1 to 3.3.0 - Added by dj jones over 8 years ago

Hi Alexander:

I hope some folks can help out.

Your findings as you go would make a great addition to some of the Wiki pages here.
eg
Plugin_Internals has not been updated for 3 years
and
Plugin_Tutorial could benefit from a sub-section on converting plugins 2->3.x

good luck!

RE: Need a strategy for updating ~70 plugins from 2.3.1 to 3.3.0 - Added by dj jones over 8 years ago

Hi Alexander

what approach have you decided on? I'm sure other RedMine readers would be interested to hear.

(1-2/2)

Project

General

Profile

Redmine