Krita 3.0.1 Release Process

Boudewijn Rempt boud at valdyas.org
Sun Aug 14 15:34:28 UTC 2016


Hi Dmitry!

Maybe you should not go into all-panic mode on a Sunday? 

On Sun, 14 Aug 2016, Dmitry Kazakov wrote:

> Hi, all!
> 
> 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"

Translators are not babies who should be spoonfed separately and specially. This
is the notification.

> What is more, noone even started merging 'stable'
> translations into 'trunk', which means they cannot even start translations,
> because 'stable' still points to 'krita/3.0' which is abandoned.

See Luigi's last mail in the "Subject: Re: Translation now set up for
"krita/3.0" branch" thread, which clearly meant, at least for me, that
I did not have to do anything. If things are not working correctly,
it's the translation community that should take action now.

> And the problem is not in the translators, but in the fact that *we* have
> no exact step-by-step release plan.  Noone is in charge of the tasks, which
> we agreed to follow during the release process [1]. We still have no way to
> control which tasks has been completed and which not. And Phabricator will
> not help us in this field. It doesn't have any Deadline capabilities:
> neither setting the date, nor automated email notifications about them.

Maybe, but I am not sure you're right.

In any case:

> https://trello.com/b/qwJfZRdf

I will not use this. Sorry, but you've wasted your time on it. I cannot
handle another way for people to make todo lists for me. I demand of
our translators that they are pro-active, subscribed to this mailing
list and capable of understanding that "string freeze" means "we can
start translating" and that if there is a problem with the setup that
they fix it ASAP or contact the right people to fix it.

I will NOT start using another tool -- tools do not fix process problems.
I will also NOT go into panic mode -- this is the first time we try the
new release cycle idea, for f's sake, why go into an all-out panic if people
don't get it? Those things need time to sink in...
-- 
Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org


More information about the kimageshop mailing list