Re: 3.0.1

Thanks Marko, that was very clear! TTU!
- -
Mathias

> Am 02.04.2022 um 19:56 schrieb Marko Lindqvist <[email protected]>:
> 
> In case we just made all this confusing, here's a plan for German translation:
> 
> - Provide your current translation by 6th Apr 21:00 UTC
> - Do not continue translating your current .po files while waiting...
> - Once I announce that I've refreshed .po files at files.freeciv.org
> with the final strings for 3.0.1, get them, and start translating
> - Provide your final translation for 3.0.1 by 13th Apr 21:00 UTC
> 
> 
> - ML
> 
> 
> On Sat, 2 Apr 2022 at 20:35, Marko Lindqvist <[email protected]> wrote:
>> 
>> You beat me in pushing "Send" ...
>> 
>> I'd add that if one already has updates to the translation + depends
>> on .po -files from files.freeciv.org, it's a good idea to provide
>> those translations before the freeze anyway. That way the update to
>> the files.freeciv.org will contain BOTH the latest English originals
>> and any updates to the translation.
>> 
>> 
>> - ML
>> 
>> On Sat, 2 Apr 2022 at 20:31, Alina Lenk <[email protected]> wrote:
>>> 
>>> Quite the opposite – string freeze is the point from which on the
>>> existing game strings, i.e. the stuff that needs translating, are no
>>> longer allowed to change. Any translation made after that point will
>>> definitely be able to make it into the release, with no risk of the
>>> original (English) string changing and making your translation invalid.
>>> (Barring very exceptional circumstances.)
>>> 
>>> The final deadline for translation updates will be a lot closer to
>>> release; generally not more than a handful of hours before the actual
>>> release.
>>> 
>>> ~AVL
>>> 
>>> Am 02.04.2022 um 19:06 schrieb Mathias (GER, Freeciv):
>>>> Do I understand this correctly: the latest moment to provide new translations would be until April 7th?
>>>> 
>>>> - -
>>>> Mathias
>>>> 
>>>>> Am 20.03.2022 um 01:50 schrieb Marko Lindqvist <[email protected]>:
>>>>> 
>>>>> Past couple of days I've been trying to decide when we should release
>>>>> 3.0.1. I think that the report about a crash bug, with fix already in
>>>>> review, ( https://www.hostedredmine.com/issues/943039 ) just resolved
>>>>> this so that we should go to release sooner rather than later. And
>>>>> looking my overall schedule I think that the "sooner" would be
>>>>> Thursday 14.4 (it's Easter weekend, so Thursday is equivalent to
>>>>> Friday when I usually make the releases) The string freeze would thus
>>>>> happen on Thursday 7.4 (00:00 EEST - 6.4 21.00 UTC)
>>>>> 
>>>>> 
>>>>> - ML
>>>>> 
>>>> 
>>> 
>