[Bf-translations-dev] i18n processes and release cycle

["志築 孝広 [Takahiro Shizuki]"]

Hi,

Please tell me for 2.62 Release,
Is the process same on 2.61?

Best regards,
shizu

Bastien Montagne さんは書きました:
> Hi,
> 
> Here is a proposition about managing bf-translations repo, and how to 
> synchronize with Blender release cycles.
> 
> * Translators should never modify themselves /trunk. They should only 
> edit /branches.
> * Translators should ask an admin to add a new language (as this also 
> implies, currently, some code in Blender).
> 
> BCon1 and BCon2:
>      New languages can be added.
>      An update of all po's under /branches is made at least once a week
>          (friday morning seems a good option, imho), and possibly more often
>          in case of big changes in sources (like a branch merged). I can 
> handle this.
>      The /trunk is also updated once a week (monday evening, imho). The 
> threshold
>          is set to 0% (i.e. all existing languages are in trunk). I can 
> also handle this.
> BCon3:
>      Like BCon1 and 2, but adding new languages is no more allowed.
> BCon4 (i.e. RC):
>      A last update of /trunk is done just before first RC, using a 
> threshold of 80% (i.e. only
>          nearly finished translations are in /trunk). Then, /trunk is no 
> more changed,
>          unless a serious issue arises (can’t imagine what, but you 
> never know…).
>      /branches remains open and updated once a week.
> BCon5 (i.e. freeze and release):
>      /trunk is also freezed (only critical bugs are fixed! :P ).
>      /branches remains open and updated once a week.
> 
> Now, fire your comments and suggestions! When we get a consensus, I’ll 
> write a wiki page about it (anyway, we lack some doc about all this!).
> 
> Best regards,
> Bastien
> _______________________________________________
> Bf-translations-dev mailing list
> Bf-translations-dev at blender.org
> http://lists.blender.org/mailman/listinfo/bf-translations-dev