Re: Milestones: i18n

Heikki Toivonen wrote:
> We will soon need Internationalization, or Localization Freeze. Once
> this is in effect, no changes will be allowed which affect localization.
> Typically this would be somewhere between Feature Freeze and Code Freeze.

I'll make the argument that we don't need this phase until later in the 
process, after we have a few Beta releases under our belts.

Brian Kirsch, Markku, PJE and others have done a great job in moving the 
i18n framework forward. Victory! Yes, there is more to do, but I think 
we're well ahead of where we need to be as a project.

Given limited resources, I think it is important that we move our 
attention to finishing up features (e.g. dashboard), improving 
performance, fixing bugs and generally stabilizing the app. I'm really 
loath to spend a lot more time on i18n at this stage in the process or 
put localization requirements on ourselves that impact project velocity 
-- we need to focus on having an app worth localizing!

Note that the above comments apply to Chandler. If I understand 
correctly, i18n is not going to be a short term focus for Cosmo, so an 
i18n freeze would not be applicable to the Cosmo process either.

Cheers,
Katie


_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general