2.20.0 release coordination with translation. Other showstoppers? (was: 2.20.0 release coordination with translation, also Germans?)

[David Kastrup]

David Kastrup <address@hidden> writes:

> Federico Bruni <address@hidden> writes:
>
>> Il giorno lun 17 feb 2020 alle 22:49, Federico Bruni
>> <address@hidden> ha scritto:
>
>>> I'm working on the italian update and I hope to be ready before 
>>> Thursday night.
>>> 
>>
>> Can we have one day delay? So deadline to push to translation branch
>> by Friday night?
>> I guess I won't have enough time to complete the update but at least I
>> can use some spare time tomorrow to get close to the goal.
>
> There was no fixed deadline.  My goal was "this weekend", but if that
> makes things ugly, there is no point in not delaying some more days
> after the years we spent on this.
>
> In unrelated news, I tried my hand at translating at least the Changes
> file into German and am about 50% done.  Anybody want to work from the
> bottom so that we should coordinate in order to avoid duplicate effort?
> I got kind of a headache so far.  Hats off to people who tackle a whole
> translation rather than just a puny file.

German Changes file has been added by now.  Where are we with regard to
the other translations?  Federico?

The plan for afterwards would generally be that we
merge/move/cherrypick/whatever translations into master without
introducing unintended regressions.  I may try doing that as I am
probably most at fault for the long 2.19.80+ phase.  For changes to doc
and translation afterwards, it will make sense to check individually
whether they can/should also go by cherry-picking into the stable branch
for the sake of possible 2.20 followup releases.  The main criterion
obviously being whether they refer to functionality actually present in
2.20.

So there is a bit of leeway for improvements in the 2.20 documentation
even after the 2.20.0 line.

-- 
David Kastrup