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

[kitlo@xxxxxxxxxx (Kit Lo)]

Ed Merks wrote:

> 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...

Hi Ed,

- the idea of the translatable strings freeze date is just to ask the 
development teams to get the majority of the translatable strings ready, 
and to think twice before changing them after the freeze date; this is 
similar to the API freeze date; we sure can handle small number of changes 
for critical bug fixes after the freeze date
- the 3 statements are just topics for discussion in the Eclipse Planning 
Council meeting; it's up to the planning council to decide if they should 
be must-do's or should-do's (of course we want all of them to be must-do's 
:-)
- the second bullet is quite important and quite easy to do; after trying 
to define the map files for a few projects ourselves, we noticed that 
every project may structure their map files in a little different way, 
it's easy for us to make mistakes and miss some of them; we are just 
asking each project to define the map files for their releases, so we can 
extract the translatable files and let all the translators around the 
world translate the files