Backport policy regarding new strings ?

Geert Janssens janssens-geert at
Mon Jan 21 11:42:23 EST 2013

Hi Yawar,

I believe I have already committed the patch for trunk in r22711. So 
with that I think the bug report can be closed.



On 20-01-13 21:57, Yawar Amin wrote:
> Hi Christian,
> On 2013-01-20 14:55, Christian Stimming wrote:
>> [...]
>> It's up to you (or anyone who wants to commit). We don't have any agreement on
>> this right now.
>> However, I would suggest not to add a new string in the 2.4.x branch. Most
>> probably, there will be no translator activity between now any another 2.4.x
>> release. This means the new string will show up untranslated. I think this
>> should be avoided, unless there are really strong reasons (for having an
>> untranslated string show up, rather than no new string and/or a string with
>> minor errors.)
>> In the case of the new tip-of-the-day, I think there is not a strong reason to
>> have it in the 2.4 branch. Just add it to trunk and it will be in the next
>> release and translation series.
>> Please feel free to add this suggestion into the wiki page... I currently
>> don't easily see how I can explain this there. Thanks!
> Thanks, I've added an explanation that should roughly cover our caution
> against adding strings
> (
> Geert, let's go ahead with Christian's suggestion to commit the patch to
> trunk but not to 2.4
> Regards,
> Yawar

More information about the gnucash-devel mailing list