Difference between revisions of "String Freeze"
(→Rules) |
(→Rules) |
||
| Line 10: | Line 10: | ||
* If you have a new feature that brings a new string, postpone it for after 2.0.0 is out. | * If you have a new feature that brings a new string, postpone it for after 2.0.0 is out. | ||
* If you think a new feature is desperately needed right now, ask on gnucash-devel, noting the string freeze violation. If there is no objection from the other developers and the translation manager ([[User:cstim]], Christian Stimming), as an exception such string additions might be allowed even during string freeze. But this is surely the exception. | * If you think a new feature is desperately needed right now, ask on gnucash-devel, noting the string freeze violation. If there is no objection from the other developers and the translation manager ([[User:cstim]], Christian Stimming), as an exception such string additions might be allowed even during string freeze. But this is surely the exception. | ||
| − | * String Freeze violations that haven't been asked | + | * String Freeze violations that haven't been asked for on gnucash-devel will be reverted. |
* String changes, on the other hand, are not at all allowed, except if the existing string is outright wrong and/or completely misleading. In any other case, including any typos, the strings must remain unchanged and the string changes must be postponed for after 2.0.0. | * String changes, on the other hand, are not at all allowed, except if the existing string is outright wrong and/or completely misleading. In any other case, including any typos, the strings must remain unchanged and the string changes must be postponed for after 2.0.0. | ||
Comments? Questions? --[[User:Cstim|Cstim]] 11:26, 16 March 2006 (EST) | Comments? Questions? --[[User:Cstim|Cstim]] 11:26, 16 March 2006 (EST) | ||
Revision as of 16:29, 16 March 2006
The GnuCash Subversion repository goes into String freeze on March xx. See Release Schedule for the schedule context on our way to a 2.0.0 release.
Purpose
The purpose of a String Freeze is to give translators enough time for translating all the strings in the application. During the String Freeze these strings are frozen and must not change; if they did change, it would mean some part of the translation work was in vain. The translators try hard to achieve 100% of translations, so that the user will not encounter any English messages anymore. This would be broken as soon as any message is changed (which will mean it will show up untranslated) or is added. To give the translators the change to achieve full translation, we will have the String Freeze period between March xx and the 2.0.0 release. Every feature addition and/or change that changes or adds strings will have to wait until 2.0.0 is out.
Rules
To ensure every developer respects this String Freeze, here's what we ask every developer:
- During string freeze you must not change or add any string.
- If you have a new feature that brings a new string, postpone it for after 2.0.0 is out.
- If you think a new feature is desperately needed right now, ask on gnucash-devel, noting the string freeze violation. If there is no objection from the other developers and the translation manager (User:cstim, Christian Stimming), as an exception such string additions might be allowed even during string freeze. But this is surely the exception.
- String Freeze violations that haven't been asked for on gnucash-devel will be reverted.
- String changes, on the other hand, are not at all allowed, except if the existing string is outright wrong and/or completely misleading. In any other case, including any typos, the strings must remain unchanged and the string changes must be postponed for after 2.0.0.
Comments? Questions? --Cstim 11:26, 16 March 2006 (EST)
