Redmine 2.1.0 and 2.0.4 released
Redmine 2.1.0 is the new feature release and is available for download at Rubyforge. It includes major and exclusive new features as well as many improvements and fixes. Here are the highlights:
- Issues and workflow improvements: you can now configure required and read-only issue fields per role, tracker and status. You can also disable core fields that you don't use on a per tracker basis.
- Issue list and filters: issues can now be filtered by custom fields defined on your projects (eg. say you have a "Customer" custom fields on your projects, you will be able to filter issues for a given customer across all projects)
- Thumbnails: you can enable the automatic display of thumbnails for images attached to an issue. And a new macro lets you add clickable thumbnails of an attached image in any formatted text (eg. wiki page, news...).
- Closed projects: a new permission is added to let project members close/reopen projects. Unlike archived projects, closed projects are still visible but the project and all its data (issues, wiki...) is read-only.
- Subtaks copy: when copying an issue, an option lets you copy subtasks too.
- REST API: Groups can now be managed through the resp API. And the REST API now supports JSONP in order to retrieve data from a server in a different domain
- Macros: macros can now accept an optional block of text, making it easy to define custom text processors.
- Internals: Redmine now uses JQuery instead of Prototype + scriptaculous
You can review the full list of changes and fixes in the changelog.
Redmine 2.0.4 is a last maintenance release for the 2.0.x branch. Redmine 1.4.x will be maintained for security updates until the end of 2012.
Comments
Added by Deoren Moor about 12 years ago
Awesome, thanks for this new release! Really excited about the upcoming changes in v2.2.0.
Added by Xing Liu about 12 years ago
How to upgrade from 2.0.3 to 2.1.0? When I upgrade the following occurs:
D:\devstudio\redmine\host\redmine-2.1.0>rake db:migrate RAILS_ENV=production
AddUniqueIndexToIssueRelations: migrating ===============================
-- add_index(:issue_relations, [:issue_from_id, :issue_to_id], {:unique=>true})
rake aborted!
An error has occurred, this and all later migrations canceled:
Index name 'index_issue_relations_on_issue_from_id_and_issue_to_id' on table 'issue_relations' already exists
Tasks: TOP => db:migrate
(See full trace by running task with --trace)
Added by Jean-Philippe Lang about 12 years ago
Remove the index you added manually then rerun the migration.
Added by Gurvan Le Dromaguet about 12 years ago
Nice content with this release ! Preparing the migration right now !
Added by Ivan Cenov about 12 years ago
What is better upgrade: from 1.4.4 directly to 2.1.0 or 1.4.4 -> 2.0.4 -> 2.1.0 ? Is there any reason for latter one ?
Added by Jean-Philippe Lang about 12 years ago
No need to upgrade to 2.0 first, upgrading from 1.4 to 2.1 is fine.
Added by rattachet settamat about 12 years ago
How to upgrade from 2.0.3 to 2.1.0?
Added by Terence Mill about 12 years ago
Please upgrade http://m.redmine.org demo Server version to 2.1
Tx for this release
Added by Jean-Philippe Lang about 12 years ago
It's on my to-do list.
Added by Jean-Philippe Lang about 12 years ago
http://m.redmine.org now runs Redmine 2.1. The environments that were used in the last 60 days were preserved and upgraded.
Added by Ivan Cenov about 12 years ago
http://m.redmine.org goes to http://m.redmine.org/hostings/new and returns