Redmine

I am pleased to announce that a Redmine book was published 2 days ago in Japan.
It's written (in Japanese) by Go Maeda, the maintainer of redmine.jp.

You can find more information on the publisher's web site (Shuwa System Co., Ltd.):
http://www.shuwasystem.co.jp/products/7980html/2137.html

Yet another bug fix release. See the Changelog for more details.
As Redmine 0.7.3 fixes several XSS vulnerabilities, users are highly encouraged to upgrade to this new release.

No database migration is needed when upgrading from previous 0.7.x versions.
This release is still running with Rails 2.0.2.

It can be downloaded at Rubyforge.

This is a bug fix release.

Like the previous 0.7.x releases, it runs with Rails 2.0.2.
Please, note that Redmine is not yet compatible with Rails 2.1 (it's planned for 0.8).

This release fixes a few bugs found in 0.7.0.
One of them is considered as severe (eg #1147), so 0.7.0 users are highly encouraged to migrate.

As usual, you can download this release at Rubyforge.

This final release brings some improvements and fixes over the RC. You can see the details in the Changelog.

• Some permissions were added to edit issue notes and time entries. You can assign them to your existing roles in Admin -> Roles & Permissions
• Issue 'edit', 'add note' and 'change status' actions are merged in a single action, accessible by clicking on the 'Update' link on the issue details view
• Bulk edit functionality is now done by right-clicking on a set of selected issues. You can select issues on the issue list by using checkboxes or by clicking on the rows (Ctrl and Shift keys can be used to select multiple issues)
• HTML tags are now escaped in wiki content (except pre and code tags)

Note that Rails 2.0.2 is now required. The downloadable release is frozen with this version of Rails and thus no particular setup is needed.

If you use svn to get Redmine and don't want to upgrade your Rails' gem, you can freeze Redmine by running the following from your Redmine directory:

rake rails:freeze:edge TAG=rel_2-0-2

As you may have noticed, redmine.org has been having some performance issues, causing some requests to time out and users to receive 500 errors.
The old server on which redmine.org was running will be upgraded in the next few days and redmine.org has just been moved to a temporary server that should handle the load.

Please, let me know if you experience any problems.

You can see what's new in this release in the changelog.

This RC release is frozen with Rails 2.0.2 and should be very close to the 0.7 final.
Upgrading from 0.6 can be done as usual with a simple database migration. Migration from 0.6 to 0.7 RC1 then to 0.7 will be of course possible.

It can be downloaded in either .tar.gz or .zip format at Rubyforge.

A potential security flaw in LDAP authentication was discovered in Redmine 0.6.3 release.
If you run Redmine 0.6.3 release and use LDAP authentication, you're highly encouraged to migrate to this new release. No database migration is needed.

Those who get Redmine using svn can simply update to the latest revision. The fix was committed in both 0.6-stable branch and trunk.

A few other bugs were fixed in this release. See the Changelog.

Just as the title says, the boards are now hosted here at redmine.org.
You are still able to read the old posts here.

TYPO3 is a free, feature rich and widely used content management system written in PHP.

The TYPO3 team have chosen Redmine for their new Forge:

For the coordination of the TYPO3 5.0 development efforts, we used to run a Trac installation which hosted our issue tracker, code browser and a wiki. But we were really missing some important features (like being able to set up sub projects) and were looking for alternatives. Fortunately, Martin Herr came across a tool called "Redmine" which looked very promising.

So we created a new website - the TYPO3 Forge. Its purpose is to centralize TYPO3's development projects and provide a home for teams who are in need of an issue tracker, code browser and subversion. Although forge.typo3.org currently accommodates only TYPO3 5.0 and FLOW3 related projects, we structured it open enough to be ready for the TYPO3 v4 team and other projects.

Read the full announcement written by Robert Lemke.