Feature #36172: Forge cleanup and update umbrella issue
Upgrade to latest redmine version
Redmine 1.2.0 has recently be released and contains a bunch of new features and fixes. Would be great to have forge updated.
#8 Updated by Karsten Dambekalns over 8 years ago
Well, 2.0.3 is current by now… No clue how much we tweaked 1.1.x and if that would cause suffering. But on http://www.redmine.org/projects/redmine/wiki/RedmineUpgrade upgrading seems easy :)
#9 Updated by Simon Schaufelberger about 8 years ago
we at punkt.de have just done an upgrade to 2.1. Everything went well but one important notice: The IDs of the priority have a different meaning now. We had a theme with priority colors and we had to change the CSS to adapt to the new ID meaning.
see http://www.redmine.org/issues/11880 for more information.
Also the Queries have changed. They might need to be edited and saved again if a status is included for example. Status IDs also have changed.
#10 Updated by Steffen Gebert about 8 years ago
Yes, your redmine wasn't hacked as much as this one here ;-)
Peter and Stefan Sprenger managed to upgrade the code base to RM 1.4
Prior to upgrading to 2.x, "we" have to rewrite all the plugins, as it seems like they've changed there plugin architecture.
Simon, thanks for the hint about the changed priorities in 2.1
#11 Updated by Jacob Floyd about 6 years ago
- translation missing: en.field_remaining_hours deleted (
For the Neos team, we need at least version 2.1.0:
As explained in COORD-6 we need to be able to close/freeze the neos and flow projects so that noone can create new issues in Forge. However that feature wasn't added to redmine until RM v2.1.0 (see feature 3640 ).
What else needs to happen to upgrade redmine?