u wrote (28 Mar 2015 18:24:45 GMT) : > intrigeri:
>> If the tools handle that just fine (e.g. by only presenting the new or
>> updated strings in topic branches), perfect. Otherwise, perhaps
>> translating stuff in devel (post-merge) or testing (post-freeze) is
>> good enough, and the benefits of allowing people to translate stuff
>> before it's deemed ready to be merged aren't worth the drawbacks.
>>
>> In short: I'd keep devel/stable/testing in SHOULD, and would simply
>> drop the MAY about topic branches unless the tools handle this use
>> case very well. > I do not have a strong opinion on this and thus agree with your proposal.
I wasn't bold enough to simply drop that MAY, but I've added a note to
the blueprint about the drawbacks we should avoid if we allow
translating topic branches (26a6ec6), so that it's clear that this
feature might actually be a bug if not implemented in a way that's
adequate for us.
