I'd say bundle 0.4.2 (unless it's known there is something bad in there), switch the syntax to the %{} format (if the gem is bundled, no problem), change the deprecation warning to not fire every time it encounters @ format and deprecate the @ format for plugins in chiliproject 2.0.

Felix Schäfer wrote:

deprecate the @@ format for plugins in chiliproject 2.0.

How about deprecating now (1.x releases)? Plugins are already throwing a ton of messages in both Redmine and ChiliProject and if we deprecate now then we can remove it in 2.x which will let us upgrade to Rails 2.3.latest (or maybe even Rails 3).

Eric Davis

I'd say we deprecate it for Bell and remove it for 2.0. We should see to let all that cruft go and smooth transition towards Rails 2.3.11.

Eric Davis wrote:

How about deprecating now (1.x releases)?

Well, I thought I was being aggressive on the schedule already, but the earlier the better :-)

Felix:

Yea, if we deprecate in 2.0 then we can't remove it until 3.0 (around February 2012!).

Eric Davis

Eric Davis wrote:

Yea, if we deprecate in 2.0 then we can't remove it until 3.0 (around February 2012!).

Hadn't thought of it that way.

Do you want to deprecate them for 1.1.0 already? If so, could you make the corresponding tickets? I'd be willing to take care of converting the existing language files.

I think 1.1.0 is already on a tight schedule. Maybe we should set aside some time to put in some depreciations into a later release, like how Rails did for the 2.3 branch once 3.0's API was standardized. (say 1.3.0 (random later release)).

Eric Davis