Alexandre Prokoudine wrote: > So translators can actually still commit translation updates to ../ > releases/2009.2? How much time do translators have?
Translators have all the time they want :) The goal of the new process is to decouple release from development; and translation is a kind of development. Translators get the same freedom as developers: you can do whatever you want in trunk; and you can help polishing the release in releases/2009.2 The only thing to pay attention to is that over time the *.po files in trunk will differ from the *.po files in the release codeline; and that changes need to be kept in sync. This could be easily achieved with a string freeze in releases/2009.2, but I would hate to do that. I'd rather move fast forward on the release, and in the meantime monitor the two codelines and sync when necessary (i.e. when the translator or developer has not done it). For release, the criteria for translation is the same as for functionality: if there is no (known) regression, it's good to go. If translations are added/polished after release, they will surely go into the next release and if there is enough support we can release a patch version (e.g. 2009.2.0 is released with translations as-is and 2009.2.1 is released with the improved translations that have arrived after 2009.2.0 was released). Yuv --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
