Upgrading from 1.4 to 2.1 vs 2.2
Added by Jared Fine almost 12 years ago
I have a Redmine 1.4 install and am considering upgrading it to 2.x. I still need to make sure the plugins are compatible, but assuming they are, which version should I upgrade them to? It seems both versions are on Rails 3.2.11. Would love the some input on this. Thanks!
Replies (6)
RE: Upgrading from 1.4 to 2.1 vs 2.2 - Added by Jan Niggemann (redmine.org team member) almost 12 years ago
I'd go for the latest possible version - if plugins permit.
RE: Upgrading from 1.4 to 2.1 vs 2.2 - Added by Ivan Cenov almost 12 years ago
These plugins work in our Redmine 2.2.2.stable. However, there is no warranty that they will work in your installation.
I posted outside Redmine site, because it says that the post is spam (may be because the too many URLs in it).
RE: Upgrading from 1.4 to 2.1 vs 2.2 - Added by Jared Fine almost 12 years ago
Jan:
That is a good point, may as well go to the most recent version, I'm a bit of a curious OCD person and would still love to see what the differences are.
Ivan:
Awesome list! It's super helpful.
RE: Upgrading from 1.4 to 2.1 vs 2.2 - Added by Jan Niggemann (redmine.org team member) almost 12 years ago
Jared, if you would like to know the differences (I take it you mean features), check out the Roadmap, here's a copy & paste of features 2.2 has and 2.1 doesn't: View details...View details...
Feature #1554: Private comments in tickets
Feature #2161: Time tracking code should respect weekends as "no work" days
Feature #3239: Show related issues on the Issues Listing
Feature #3265: Filter on issue relations
Feature #3447: Option to display the issue descriptions on the issues list
Feature #3511: Ability to sort issues by grouped column
Feature #4590: Precede-Follow relation should move following issues when rescheduling issue earlier
Feature #5487: Allow subtasks to cross projects
Feature #6899: Add a relation between the original and copied issue
Feature #7082: Rest API for wiki
Feature #9835: REST API - List priorities
Feature #10789: Macros {{child_pages}}
with depth parameter
Feature #10852: Ability to delete a version from a wiki page history
Feature #10937: new user format #{lastname}
BTW, 2.3 is due in 14 days. It will bring: View details...View details...
Feature #1766: Timelog custom-field columns should become addable to 'Spent Time'-details report.
Feature #3436: Show relations in Gantt diagram
Feature #3957: Ajax file upload with progress bar
Feature #5298: Store attachments in sub directories
Feature #5605: Subprojects should (optionally) inherit Members from their parent
Feature #6727: Add/remove issue watchers via REST API
Feature #7159: Bulk watch/unwatch issues from the context menu
Feature #8579: Multiple file upload with HTML5 / Drag-and-Drop
Feature #10191: Add Filters For Spent time's Details and Report
Feature #10286: Auto-populate fields while creating a new user with LDAP
Feature #10352: Preview should already display the freshly attached images
Feature #12122: Gantt progress lines (html only)
Feature #12228: JRuby 1.7.2 support
Feature #12251: Custom fields: 'Multiple values' should be able to be checked and then unchecked
Feature #12401: Split "Manage documents" permission into create, edit and delete permissions
Feature #12542: Group events in the activity view
Feature #12665: Link to a file in a repository branch
Feature #12713: Microsoft SQLServer support
Feature #12787: Remove "Warning - iconv will be deprecated in the future, use String#encode instead."
Feature #12843: Add links to projects in Group projects list
Feature #12898: Handle GET /issues/context_menu parameters nicely to prevent returning error 500 to crawlers
Feature #12913: Update RedmineInstall to reflect recent changes in install doc in source upon new release
Feature #12992: Make JSONP support optional and disabled by default
Feature #11502: Expose roles details via REST API
Feature #11755: Impersonate user through REST API auth
Feature #12085: New user name format: firstname + first letter of lastname
Feature #12125: Set filename used to store attachment updloaded via the REST API
Feature #12167: Macro for inserting collapsible block of text
Feature #12211: Wrap issue description and its contextual menu in a div
Feature #12216: Textual CSS class for priorities
Feature #12299: Redmine version requirement improvements (in plugins)
Feature #12393: Upgrade to Rails 3.2.9
Feature #12475: Lazy loading of translation files for faster startup
Edit by Mischa The Evil: fixed unwanted macro execution.
RE: Upgrading from 1.4 to 2.1 vs 2.2 - Added by Jared Fine almost 12 years ago
Ah, gotcha. So for the most part each version is really just adding features not really breaking backwards compatibility. So if doing a major release upgrade there really isn't much of a reason to not go latest. Thanks Jan!
RE: Upgrading from 1.4 to 2.1 vs 2.2 - Added by Jan Niggemann (redmine.org team member) almost 12 years ago
Jared Fine wrote:
So if doing a major release upgrade there really isn't much of a reason to not go latest. Thanks Jan!
Except for the not-so-rare case that beloved plugins don't always support the latest cutting-edge version ;-)