[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-kimageshop
Subject: Re: Krita 3.0.1 Release Process
From: Wolthera <griffinvalley () gmail ! com>
Date: 2016-08-18 14:08:00
Message-ID: CAN80MtGan4pXR021ZdwGghVbcMd2mko=i+=qZcaTBTkOVtOWhw () mail ! gmail ! com
[Download RAW message or body]
The 3.0.1 release announcement and the docs are already done, that's
something Scott and I take care of. (Release announcement needs a few
images and maybe links, but we have two full weeks)
The only thing that really hiccups is translations, because that is a
separate group of people with a completely different system(like, they
don't even use git).
If you want to set a formal deadline for the announcements, talk to me and
scott?
Op 18 aug. 2016 14:54 schreef "Dmitry Kazakov" <dimula73@gmail.com>:
> Ok, Boud. Then I will just not take part in this release. No announcements
> for the 2.5k people in vk community, no habrahabr post with 100k+ people
> reading it, no help with translations, nothing except of bugfixes for the
> bugs you add to the phabricator board.
>
> To make announcements or coordinate translators I need to have information
> about the release. The announcement should be ready in at least a day or
> two before the day of the release, so I could delegate translation to
> anyone and don't get up at six in the morning at the day of the release to
> translate it myself. The translators should be notified that the builds are
> coming so they could push the changes to SVN. Not all the translators have
> an SVN commit access, so this process is not superfast. From this point of
> view 3.0 release was a failure. Due to the fact that everything has been
> done at the last day, I couldn't delegate anything and had to do everything
> myself. Though there were people who could do it instead of me if they were
> notified in time.
>
> Just try to understand that your are not the only person in this project.
> And not all the people who involved into the process are motivated enough
> to sit on IRC all day long and read all the messages just to know when the
> builds are ready, or are going to be ready.
>
>
>
> On Thu, Aug 18, 2016 at 2:17 PM, Boudewijn Rempt <boud@valdyas.org> wrote:
>
>> On Tue, 16 Aug 2016, Dmitry Kazakov wrote:
>>
>> I was surprised to read on irc that I apparently still have
>> to make a decision about using Trello or not. I would have
>> assumed my last mail was clear enough, but in case it wasn't:
>>
>> No, we will not use Trello this release cycle. We will do this
>> release cycle like we agreed upon on July 18th, as documented
>> originally in this google doc:
>>
>> https://docs.google.com/document/d/1wFfOD8ce-8MD8tYD8FrXIgVL
>> JwkXtMSEHi_IPQ0yMGI/edit
>>
>> Which contains the notes we made during that meeting.
>>
>> After the release we can discuss whether we need improvements
>> or whether everything went fine. When it comes to planning,
>> there are absolutely no surprises:
>>
>> https://calendar.google.com/calendar/embed?src=pv232t7pu0acs
>> tl5c64357mlo4%40group.calendar.google.com&ctz=Europe/Amsterdam
>>
>> Making dev builds during the stabilization phase happens whenever
>> I or someone else has time for it. I tend to do those in the
>> weekends and try to release on Monday. Those are not really
>> releases, though for clarities' sake, I might call them alpha's
>> or beta's. But they come out whenever I have time or energy.
>>
>> I would like to remind everyone that
>>
>> a) we made 12 2.9 releases and that went almost always completely
>> fine, with very minor hickups.
>>
>> b) nothing major went "wrong" that merited all the stress.
>>
>> c) because we release often we can afford to be less stressed
>> about releases. If something slips through, take a deep breath,
>> it's not the end of the world and not a reason to stress out. It
>> can be fixed in the next release, and in the meantime we get
>> used again to frequent releases and things will keep going
>> smoother.
>>
>> d) In contrast to 3.0, where we actually didn't even have a
>> source release, we will have that for 3.0.1 -- that's something
>> to be happy about! The source tarballs will also contain the
>> latest transslations automatically, and we'll build the binaries
>> from the source tarballs -- which is a major step because before
>> they were made from git.
>>
>> Finally, I have been home sick for nearly two months now. Burn-out
>> is a serious condition and I can do with a lot less stress. Stress
>> happens not because I have something that needs to be done, it happens
>> when someone decides that I need to do something, or need to do
>> something in a different way. That needs to be avoided.
>>
>> I hope that this is clear.
>> --
>> Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
>>
>
>
>
> --
> Dmitry Kazakov
>
[Attachment #3 (text/html)]
<p dir="ltr">The 3.0.1 release announcement and the docs are already done, that's \
something Scott and I take care of. (Release announcement needs a few images and \
maybe links, but we have two full weeks)</p> <p dir="ltr">The only thing that really \
hiccups is translations, because that is a separate group of people with a completely \
different system(like, they don't even use git).</p> <p dir="ltr">If you want to \
set a formal deadline for the announcements, talk to me and scott?</p> <div \
class="gmail_extra"><br><div class="gmail_quote">Op 18 aug. 2016 14:54 schreef \
"Dmitry Kazakov" <<a \
href="mailto:dimula73@gmail.com">dimula73@gmail.com</a>>:<br \
type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Ok, Boud. \
Then I will just not take part in this release. No announcements for the 2.5k people \
in vk community, no habrahabr post with 100k+ people reading it, no help with \
translations, nothing except of bugfixes for the bugs you add to the phabricator \
board.<br><br></div>To make announcements or coordinate translators I need to have \
information about the release. The announcement should be ready in at least a day or \
two before the day of the release, so I could delegate translation to anyone and \
don't get up at six in the morning at the day of the release to translate it \
myself. The translators should be notified that the builds are coming so they could \
push the changes to SVN. Not all the translators have an SVN commit access, so this \
process is not superfast. From this point of view 3.0 release was a failure. Due to \
the fact that everything has been done at the last day, I couldn't delegate \
anything and had to do everything myself. Though there were people who could do it \
instead of me if they were notified in time.<br><br></div>Just try to understand that \
your are not the only person in this project. And not all the people who involved \
into the process are motivated enough to sit on IRC all day long and read all the \
messages just to know when the builds are ready, or are going to be \
ready.<br><div><br><br></div></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Thu, Aug 18, 2016 at 2:17 PM, Boudewijn Rempt <span \
dir="ltr"><<a href="mailto:boud@valdyas.org" \
target="_blank">boud@valdyas.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">On Tue, 16 Aug 2016, Dmitry Kazakov wrote:<br> <br>
I was surprised to read on irc that I apparently still have<br>
to make a decision about using Trello or not. I would have<br>
assumed my last mail was clear enough, but in case it wasn't:<br>
<br>
No, we will not use Trello this release cycle. We will do this<br>
release cycle like we agreed upon on July 18th, as documented<br>
originally in this google doc:<br>
<br>
<a href="https://docs.google.com/document/d/1wFfOD8ce-8MD8tYD8FrXIgVLJwkXtMSEHi_IPQ0yMGI/edit" \
rel="noreferrer" target="_blank">https://docs.google.com/docume<wbr>nt/d/1wFfOD8ce-8MD8tYD8FrXIgVL<wbr>JwkXtMSEHi_IPQ0yMGI/edit</a><br>
<br>
Which contains the notes we made during that meeting.<br>
<br>
After the release we can discuss whether we need improvements<br>
or whether everything went fine. When it comes to planning,<br>
there are absolutely no surprises:<br>
<br>
<a href="https://calendar.google.com/calendar/embed?src=pv232t7pu0acstl5c64357mlo4%40group.calendar.google.com&ctz=Europe/Amsterdam" \
rel="noreferrer" target="_blank">https://calendar.google.com/ca<wbr>lendar/embed?src=p \
v232t7pu0acs<wbr>tl5c64357mlo4%40group.<wbr>calendar.google.com&ctz=<wbr>Europe/Amsterdam</a><br>
<br>
Making dev builds during the stabilization phase happens whenever<br>
I or someone else has time for it. I tend to do those in the<br>
weekends and try to release on Monday. Those are not really<br>
releases, though for clarities' sake, I might call them alpha's<br>
or beta's. But they come out whenever I have time or energy.<br>
<br>
I would like to remind everyone that<br>
<br>
a) we made 12 2.9 releases and that went almost always completely<br>
fine, with very minor hickups.<br>
<br>
b) nothing major went "wrong" that merited all the stress.<br>
<br>
c) because we release often we can afford to be less stressed<br>
about releases. If something slips through, take a deep breath,<br>
it's not the end of the world and not a reason to stress out. It<br>
can be fixed in the next release, and in the meantime we get<br>
used again to frequent releases and things will keep going<br>
smoother.<br>
<br>
d) In contrast to 3.0, where we actually didn't even have a<br>
source release, we will have that for 3.0.1 -- that's something<br>
to be happy about! The source tarballs will also contain the<br>
latest transslations automatically, and we'll build the binaries<br>
from the source tarballs -- which is a major step because before<br>
they were made from git.<br>
<br>
Finally, I have been home sick for nearly two months now. Burn-out<br>
is a serious condition and I can do with a lot less stress. Stress<br>
happens not because I have something that needs to be done, it happens<br>
when someone decides that I need to do something, or need to do<br>
something in a different way. That needs to be avoided.<br>
<br>
I hope that this is clear.<br>
<div><div>--<br>
Boudewijn Rempt | <a href="http://www.krita.org" rel="noreferrer" \
target="_blank">http://www.krita.org</a>, <a href="http://www.valdyas.org" \
rel="noreferrer" target="_blank">http://www.valdyas.org</a><br> \
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div \
data-smartmail="gmail_signature">Dmitry Kazakov</div> </div>
</blockquote></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic