Krita 3.0.1 Release Process

[Alexander Potashev]

2016-08-14 19:58 GMT+03:00 Dmitry Kazakov <dimula73 at gmail.com>:
>
>> > It seems like our current release process got failed again. The
>> > translators
>> > were not notified that the merge window got closed and they can start
>> > doing
>> > translations.
>>
>> I think the translators were notified: we had a mail to the mailing list
>> saying
>>
>> "Subject: Krita Planning: String freeze and bugfix phase going from
>> August 08,  2016 at 12:00PM till September 04, 2016 at 12:00PM"
>
>
>
> That was a Krita mailing list, not the translators one. And what I
> understood from the Alexander, there is no understanding what they should
> do.

Dmitry,

The process of merging translations back and forth is internal to a
translation team, it's not something that can be handled universally
for all languages. As for Russian, I had to copy the .po files in SVN
from branches/stable into trunk because the stable branch contained
the most complete set of Russian translations.

You are right about the notification email:
 1. It hasn't been sent into kde-i18n-doc mailing list,
 2. It did not mention the SVN branch one should translate in, IOW
"what they [translators] should do".

Another thing missing is a notification for I18n coordinators (e.g.
Luigi Toscano) in kde-i18n-doc that you (Krita) are going to switch
Git branches available for translation, so that they assign Git
branches to the right i18n branches in SVN and move/delete the
existing translations if necessary. From what I have understood, the
Krita project now maintains only one master branch (like KDE
Frameworks does), thus a reasonable request to i18n coordinators would
be to delete Krita translations from branches/stable/l10n-kf5/ and
configure extraction from krita.git's branch master into
trunk/l10n-kf5/.

-- 
Alexander Potashev