Project

General

Profile

Actions

Task #2800

closed

Redmine upgrade to 4.0

Added by Florian Effenberger about 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Redmine
Target version:
Team - Q4/2019
Start date:
Due date:
% Done:

100%


Description

As basis for further developments, we should evaluate installing Redmine 4.0, so we have a stable basis also for some plugins to deploy.
When doing the upgrade, please also check if there are updates to the installed plugins and themes.


Related issues

Precedes Infrastructure - Task #2801: Redmine reminder e-mailsClosedGuilhem Moulin

Actions
Actions #1

Updated by Florian Effenberger about 5 years ago

  • Category set to Redmine
Actions #2

Updated by Florian Effenberger about 5 years ago

  • Precedes Task #2801: Redmine reminder e-mails added
Actions #3

Updated by Florian Effenberger about 5 years ago

  • Description updated (diff)
Actions #4

Updated by Florian Effenberger almost 5 years ago

Does it make sense to handle that before the SSO comes to play?

Actions #5

Updated by Guilhem Moulin almost 5 years ago

  • Target version changed from Q1/2019 to Q2/2019

I think it makes sense to defer that to after the migration, given the plugins and migration path have been tested for 3.x only.

Actions #6

Updated by Florian Effenberger almost 5 years ago

Hm... if 3.x becomes EOL, aren't we locked then?
How much work is testing the path with 4.x, just to be sure we're
heading the right direction?

Actions #7

Updated by Guilhem Moulin almost 5 years ago

Florian Effenberger wrote:

Hm... if 3.x becomes EOL, aren't we locked then?

An EOL doesn't necessarily means it's game over :-) FWIW there are plenty of distros serving old versions and backporting CVE fixes. That said for such a big monolithic front-end software I'd prefer to stick to upstream's EOL schedule. No EOL has been announced for 3.x, and given their previous release schedule I'd say that's unlikely to happen before 4.1 is released.

How much work is testing the path with 4.x, just to be sure we're heading the right direction?

We're heading in the right direction, one step at the time :-)

Actions #8

Updated by Florian Effenberger almost 5 years ago

An EOL doesn't necessarily means it's game over :-) FWIW there are
plenty of distros serving old versions and backporting CVE fixes. That
said for such a big monolithic front-end software I'd prefer to stick to
upstream's EOL schedule. No EOL has been announced for 3.x, and given
their previous release schedule I'd say that's unlikely to happen before
4.1 is released.

Ok, I trust your judgement here then :-)

Actions #9

Updated by Florian Effenberger almost 5 years ago

  • Target version changed from Q2/2019 to Q3/2019
Actions #10

Updated by Guilhem Moulin over 4 years ago

  • Status changed from New to Closed
  • Target version changed from Q3/2019 to Q4/2019
  • % Done changed from 0 to 100

Done, works fine AFAICT, but I had to disable ‘quick_view’ and ‘progressive_projects_list’ plugins. The former looks dead upstream, for the later we might be able to reactivate again soon: https://github.com/stgeneral/redmine-progressive-projects-list/issues/86 .

Actions

Also available in: Atom PDF