How do we manage translation effort in Release process/roadmap?

[Korakurider]

Hi, all.
I have read though Greg's release process draft of OLPC
(http://wiki.laptop.org/go/Release_Process_Home)
and ReleaseTeam/Roadmap of SugarLabs
(http://wiki.sugarlabs.org/go/ReleaseTeam/Roadmap).
But both draft documents haven't explained translation of software
(including activity) and others.

Until midst of update.1 development, development of activities and
translation had been aligned to the road map
of XO software.  it was straightforward; we were notified when window
for translation of whole project was opened/closed.

Now our collaboration has become complex, because of SugarLabs's split.
Translators are still working with one unified portal (i.e Pootle),
but I can't understand how and when each PO will be pulled to build.
Without those knowledge it would be difficult for translation
community to manage their schedule.
Could you please explain about this?

For instance, scheduled build of Terminal activity with pulling newer
translation was announced recently.
(http://lists.laptop.org/pipermail/localization/2008-June/001138.html)
 So we could easily manage the effort.
But could we expect similar announcement for every activities, or will
the window for translation of activity aligned to
development road map of sugarlab or OLPC?

Maybe I missed important thing, though...

Thanks in advance
/Korakurider