A couple of hours ago I upgraded the code domain from Redmine 0.8.0 to Redmine 0.9.0, currently available in pre-beta.
Redmine 0.9.0 offers tons of improvements but one among all forced my decision to upgrade without waiting for a final release: Rails 2.3.5. Redmine 0.8.x is built on Rails 2.1.0 and there seems to be some kind of weird Rails-Redmine-Passenger-Ruby EE memory leaks.
With the new release, Redmine has changed the most part of its URLs. The development team basically migrated all routes to a more RESTful-oriented architecture. They did a wonderful job, unfortunately they probably chose the worst way to ensure backward-compatibility: duplication.
All the old routes are still available along with the new ones and this can cause several duplicate content issues. To patch the problem, I configured some Apache redirection rules in order to permanently redirect the old URLs to the new ones.
The gist doesn’t pretend to solve all issues. It’s just a quick and (quite) dirty fix.
From Redmine side, I would have setup a Rails Metal to redirect all the old URLs to the new ones. This is not as efficient as relying on the web server, but this is compatible with any user environment.
Feel free to fork, clone and update the gist. After all, this is a Git repository!
I don’t want to seem pedantic here, but you could have filed a feature/bug for this, or maybe even a patch :-) On the other hand, you are right that the routes in redmine are a mess right now, maybe we could get this fixed for 1.0.
I’m used to file bugs and submit patches to Redmine but I wanted to wait for the final release before formulating a full ticket.