ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Deprecate the catch-all route (Feature #435)

Added by Felix Schäfer at 2011-05-29 03:15 pm. Updated at 2011-05-29 06:17 pm.

Status:Open Start date:2011-05-29
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:Refactoring
Target version:-
Remote issue URL: Affected version:master

Description

I think we've talked about deprecating the catch-all route already, but before removing it we should deprecate it. I'm not sure how that should be communicated, but I'd like to deprecate it in 2.0 and throw it out in 3.0 at the latest.

History

#1
Updated by Eric Davis at 2011-05-29 06:17 pm

I'd like to deprecate this in the 2.x series but I don't want to block 2.0.0 with it. The deprecation warning could just be a forum message and wiki page.

(I'm thinking that each major deprecation should have a wiki page. That way we can point someone to a specific page that shows when it was deprecated, when it was (will be) removed, and how to upgrade.)

  • Target version deleted (2.0.0)

Also available in: Atom PDF