[Localization] Contribution support request

[Oswald Buddenhagen]

On Wed, Sep 13, 2023 at 06:13:47PM +0200, LittleWhite wrote:
>> Note that unlike the rest of Qt, the translations still use a 
>> forward-merging branch model, so you should target the oldest branch 
>> you find still relevant first
>
>First, it is in the "Instructions for Qt", so, not sure if I should 
>follow it, or not (I mean, when contributing to Qt Creator). 
>
qtc as a whole still uses forward-merging, so it's kind of redundant to 
mention it in the translation wiki. also, the wiki links to the in-tree 
readme, which has something to say about it.

>I also find it cryptic because you have to follow recent Qt Creator 
>development to understand that this branch is the (actually) 11.0. I 
>mean, what would be the way to get this info? [...]
>
yeah, the process sort of assumes that you get yourself informed about 
the current release, whichever way. the l10n wiki even asks for talking 
to us ...
theoretically there is https://wiki.qt.io/Branches, but of course it's 
totally outdated.
once upon a time you could sort of rely on 
https://l10n-files.qt.io/l10n-files/ having the right info, but tqtc did 
its best to suffocate this service.

>For beginners, the forward-merging branch model may not make that much 
>sense.
>
i find that debatable even as a general statement.
but specifically for translations it makes no sense to me at all - as a 
translator i want to work with something halfways stable. that's what 
string freezes are all about, after all. that makes a dev-first model an 
inherently bad match for translations.

i can see how that doesn't come naturally for someone coming from web 
apps which do continuous deployment, but the qt project works with 
traditional release cycles, which is kind of obvious.

regards