This makes me think...
What about reverting the "official" i18n namespace to ".../i18n/2.0" as it was before ? This would allow warning-less compatibility of 2.0 applications and avoid breaking lots of docs, books, articles, etc.
Of course, we should provide "legacy" support for the "../i18n/2.1" namespace as it has been released (damn, wish I did this a few days before).
What do you think ?
How about making them synonyms, i.e. giving them an equals status?
+1
The new namespace is already in Cocoon 2.1 for a very long time, and I think many people started to depend on it.
Sylvain does not want to remove 2.1 support, but only make 2.0 the official one. But even this is a bit strange to explain to users :-)
Joerg
