[News.eclipse.foundation] Re: Galileo release plan, and how it will fit

[Ed Merks <Ed.Merks@xxxxxxxxx>]

Kit,

Of course history tells us that development issues will definitely come 
up such that a small number of translatable strings trickle in after the 
planned cutoff date.  I get the impression that our processes are so 
well thought out that a small number of late arrivals would be easily 
handled.  I notice that all these statements are should-do.  Is is 
possible to participate in Babel without doing at least the second 
bullet?  If not, perhaps that one should be first in the list and should 
be a must-do...


Kit Lo wrote:
> I've proposed the following 3 Babel topics for discussion in the up 
> coming Eclipse Planning Council meeting. The chair of the Planning 
> Council Rich Gronback has already added Babel participation as a 
> Must-Do requirement for the Galileo release, and indicated an M6 
> completion date.
>
> - each Eclipse project should add the Babel Pseudo Translation Test to 
> their release plan to make sure their project is properly globalized, 
> with all strings externalized, and all layout problems fixed
> - each Eclipse project should define their project map files at the 
> Babel Translation Server so translators around the world could help 
> translating the Eclipse project
> - each Eclipse project should freeze their translatable strings at M6 
> to give translators enough time for translation before project release 
> date