[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-kimageshop
Subject: Re: 16/11/2015 Meeting minutes
From: Dmitry Kazakov <dimula73 () gmail ! com>
Date: 2015-11-26 6:49:10
Message-ID: CAEkBSfXQ2CqU6oGXgx+EkbHu=VZCMar-mKvYEVWC-LLbtbbNmQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
yeah :(
On Wed, Nov 25, 2015 at 11:56 PM, Boudewijn Rempt <boud@valdyas.org> wrote:
> Because too tired to start yet another wiki page nobody finds:
>
> we MUST BUMP the krita.rc version number before releasing.
>
> --
> Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
>
> On Tue, 24 Nov 2015, Boudewijn Rempt wrote:
>
> ANother thing we shouldn't forget for the checklist: for major releases,
> > the info booklet must be updated, and sent out to journalists at least a
> > month before the release.
> >
> > --
> > Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
> >
> > On Thu, 19 Nov 2015, Boudewijn Rempt wrote:
> >
> > Mostly from the excellent notes, filled in to follow the agenda:
> > >
> > > = Minutes for Planning Meeting 16.11.2015 =
> > >
> > > # Notes from the meeting [
> > > https://notes.kde.org/p/krita-meeting-2015-11-16 etherpad-link]
> > >
> > > # Release process
> > >
> > > Now that we're on our own, we need to improve our release process.
> > >
> > > ## Calendar/Checklist:
> > >
> > > We need to develop a release checklist. An example is
> > > http://wiki.blender.org/index.php/Dev:Doc/Process/Release_Checklist,
> > >
> > > Here is what we have until now:
> > >
> > > Release Checklist:
> > > * Write release post.
> > > * Changing the git version number.
> > > * Add a git-tag
> > > * Ping all translators team in a week before the packages build
> > > * Create translations tarball (dmitryK)
> > > * OSX build
> > > * Windows build(does it crash?)
> > > * Testing packages on:
> > > *Ubuntu(launchpad)
> > > *Arch
> > > *OpenSuse
> > > * Naming sceme
> > >
> > > Once we have defined a release schedule (task for Boudewijn), we will
> > > setup
> > >
> > a
> >
> > > shared calendar that can send out reminders:
> > >
> > >
> > > [
> > https://calendar.google.com/calendar/embed?src=pv232t7pu0acstl5c64357mlo4%40group.calendar.google.com&ctz=Europe/Moscow
> >
> > > Krita Release Calendar]
> > >
> > > We're going back to one big release a year, with bugfix/small feature
> > > releases every month:
> > >
> > > Large releases VS Small Releases:
> > > Large releases are a change in the Y in X.Y.Z
> > > * These contain large features.
> > > * Are ideally released in March so that bugs can be fixed before
> > >
> > May(the
> >
> > > kickstarter month)
> > > * Feature freeze at the least two month before expected release?
> > > * String freeze at the least two weeks before final release?
> > > Small releases are a change in Z in X.Y.Z
> > > * These contain bugfixes that weren't wishbugs.
> > > * And they contain small features. So new actions, tweaked hotkeys,
> > > a small modification to a c-plugin. No big feature changed in the core.
> > > * Feature freeze at the least two weeks before expected release?
> > > * String freeze at the least one week before final release?
> > > * Write marketing material(feature demo video/manual item/etc)
> > > around feature freeze.
> > > Features:
> > > Big features need to go into testing branches:
> > > * These are named testing-commiter or featurename-commiter
> > > * So do changes to the defaults. We have endusers use our master
> > > branch, let s wanr them before making big changes.
> > > * Branch merges into master need CCMAIL:kimageshop@kde.org
> > > Testing-releases:
> > > Alpha: Main features kickstarter+as many stretchgoals as we can fit.
> > > Beta:Real freeze in january. Bugfixing time!
> > > Final: Ideally done in March.
> > >
> > > ## 3.0 Release schedule and contents
> > >
> > > * 3.0.0 pre-alpha: December 1st --- work as usual. Fix tablet support
> > > * 3.0.0 alpha: January 6th --- Feature Freeze, tablet support + 1-2
> > > stretch goals.
> > > Priority features:
> > > * lazy brush (because it would add uniqueness)
> > > * Layer docker redesign.
> > > * multi-layer selection improvements
> > > * exporting to animated formats
> > >
> > > * 3.0.0 beta: February 3rd
> > > * 3.0.0 final: March 2nd
> > >
> > > ## 3.1 Release schedule and contents
> > >
> > > * 3.1 --- 13th of April
> > >
> > > ## 2.9 How many releases are left? 2.9.10, 2.9.11...
> > >
> > > * 2.9.10: December 2nd
> > >
> > > ## 2.9 Animation. 2.9-based test releases for Windows and Linux (without
> > > translations).
> > >
> > > Will be released 26th of November. See the checklist in the meeting
> > > notes.
> > >
> > > ## Branching
> > >
> > > Branches:
> > > 3.0 has the main branch for the feature frozen code
> > > 3.0.1 tag that points to the released version
> > > If the released version was cancelled due to a blocker but, we
> > > branch into 3.0.1.1 and cherry-pick neded commits there
> > >
> > >
> > > # Coding Priorities
> > >
> > > For 3.0, Dmitry will work on tablet support, missing features for
> > >
> > animation,
> >
> > > multilayer handling, layer docker improvements. Scott will work on a
> > > design for the improved layer docker.
> > >
> > > Missing animation features:
> > >
> > > * exporting frames to APNG/GIF/Spritesheet(This is a stretchgoal too)
> > > * cross-layer D&D
> > > * merging and other whole-image actions
> > >
> > > For 3.0, Boud is working on import/export of gimp brushes, general qt5
> > > porting and now also on the OSX port...
> > >
> > > Abrahams is creating new action system, therefore requests we take
> > > action related stretchgoals to him first for discussion. So when adding a
> > > feature and/or stretchgoal, please ask Abrahams about how to implement
> > > shortcuts
> > >
> > > Abrahams has finished work on tablet support for Windows. We're back at
> > > a fork of the Qt code... But we'll try to keep the delta small so we can
> > > upstream patches to eCloud. For x11, that's hard since the tablet support
> > >
> > is
> >
> > > all over the xcb qpa (Qt platform abstraction for the new X11 api).
> > >
> > > ## Vc 1.0 port
> > >
> > > Not much code needed, but let's push the change to a branch first so we
> > > can do a thorough regression test.
> > >
> > > ## 3.0 Tablet support
> > >
> > >
> > > Abrahams has finished work on tablet support for Windows. We're back at
> > > a fork of the Qt code... But we'll try to keep the delta small so we can
> > > upstream patches to eCloud. For x11, that's hard since the tablet support
> > >
> > is
> >
> > > all over the xcb qpa (Qt platform abstraction for the new X11 api).
> > >
> > > ## A man from St. Petersburg wants to create a UIX design of tablet
> > >
> > interface
> >
> > > for Krita (no coding, just the design)
> > >
> > > This is a uni project, there might be some funding involved. Dmitry will
> > >
> > stay
> >
> > > in contact, this person's English is not great.
> > >
> > > ## Documents on the wiki need a bit of love.
> > >
> > > * Dmitry make a mail about directory listing in wiki
> > > * Current manual writers will focus on userbase.
> > > * Scottyp is investigating mediawiki alternatives.
> > >
> > > # Sprint
> > > ## Mini sprint in Q1, or a maxi sprint in Q2?
> > >
> > > Both, we'll have a sprintlet in Deventer with at least Dmitry in
> > > February. Everyone else is welcome, but there might not be funding for a
> > > lot of
> > >
> > travel!
> >
> > >
> > > Boud will contac the e.V. board about a KDE sponsored big sprint in Q2.
> > >
> > > --
> > > Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
> > > _______________________________________________
> > > Krita mailing list
> > > kimageshop@kde.org
> > > https://mail.kde.org/mailman/listinfo/kimageshop
> > >
> > > _______________________________________________
> > Krita mailing list
> > kimageshop@kde.org
> > https://mail.kde.org/mailman/listinfo/kimageshop
> >
> > _______________________________________________
> Krita mailing list
> kimageshop@kde.org
> https://mail.kde.org/mailman/listinfo/kimageshop
>
--
Dmitry Kazakov
[Attachment #5 (text/html)]
<div dir="ltr">yeah :(<br><br></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Wed, Nov 25, 2015 at 11:56 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">Because too tired to start yet another wiki page nobody \
finds:<br> <br>
we MUST BUMP the krita.rc version number before releasing.<span class="im \
HOEnZb"><br> <br>
-- <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> <br></span><div \
class="HOEnZb"><div class="h5"> On Tue, 24 Nov 2015, Boudewijn Rempt wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> ANother thing we shouldn't forget for the checklist: for \
major releases, the info booklet must be updated, and sent out to journalists at \
least a month before the release.<br> <br>
-- <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> <br>
On Thu, 19 Nov 2015, Boudewijn Rempt wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> Mostly from the excellent notes, filled in to follow the \
agenda:<br> <br>
= Minutes for Planning Meeting 16.11.2015 =<br>
<br>
# Notes from the meeting [<a href="https://notes.kde.org/p/krita-meeting-2015-11-16" \
rel="noreferrer" target="_blank">https://notes.kde.org/p/krita-meeting-2015-11-16</a> \
etherpad-link]<br> <br>
# Release process<br>
<br>
Now that we're on our own, we need to improve our release process.<br>
<br>
## Calendar/Checklist:<br>
<br>
We need to develop a release checklist. An example is <a \
href="http://wiki.blender.org/index.php/Dev:Doc/Process/Release_Checklist" \
rel="noreferrer" target="_blank">http://wiki.blender.org/index.php/Dev:Doc/Process/Release_Checklist</a>,<br>
<br>
Here is what we have until now:<br>
<br>
Release Checklist:<br>
* Write release post.<br>
* Changing the git version number.<br>
* Add a git-tag<br>
* Ping all translators team in a week before the packages build<br>
* Create translations tarball (dmitryK)<br>
* OSX build<br>
* Windows build(does it crash?)<br>
* Testing packages on:<br>
*Ubuntu(launchpad)<br>
*Arch<br>
*OpenSuse<br>
* Naming sceme<br>
<br>
Once we have defined a release schedule (task for Boudewijn), we will setup <br>
</blockquote>
a <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> shared calendar that can send out reminders:<br>
<br>
<br>
</blockquote>
[<a href="https://calendar.google.com/calendar/embed?src=pv232t7pu0acstl5c64357mlo4%40group.calendar.google.com&ctz=Europe/Moscow" \
rel="noreferrer" target="_blank">https://calendar.google.com/calendar/embed?src=pv232t7pu0acstl5c64357mlo4%40group.calendar.google.com&ctz=Europe/Moscow</a> \
<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> Krita Release Calendar]<br>
<br>
We're going back to one big release a year, with bugfix/small feature releases \
every month:<br> <br>
Large releases VS Small Releases:<br>
Large releases are a change in the Y in X.Y.Z<br>
* These contain large features.<br>
* Are ideally released in March so that bugs can be fixed before <br>
</blockquote>
May(the <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> kickstarter month)<br>
* Feature freeze at the least two month before expected release?<br>
* String freeze at the least two weeks before final release?<br>
Small releases are a change in Z in X.Y.Z<br>
* These contain bugfixes that weren't wishbugs.<br>
* And they contain small features. So new actions, tweaked hotkeys, a small \
modification to a c-plugin. No big feature changed in the core.<br>
* Feature freeze at the least two weeks before expected release?<br>
* String freeze at the least one week before final release?<br>
* Write marketing material(feature demo video/manual item/etc) around feature \
freeze.<br> Features:<br>
Big features need to go into testing branches:<br>
* These are named testing-commiter or featurename-commiter<br>
* So do changes to the defaults. We have endusers use our master branch, \
let s wanr them before making big changes.<br>
* Branch merges into master need <a \
href="mailto:CCMAIL%3Akimageshop@kde.org" \
target="_blank">CCMAIL:kimageshop@kde.org</a><br> Testing-releases:<br>
Alpha: Main features kickstarter+as many stretchgoals as we can fit.<br>
Beta:Real freeze in january. Bugfixing time!<br>
Final: Ideally done in March.<br>
<br>
## 3.0 Release schedule and contents<br>
<br>
* 3.0.0 pre-alpha: December 1st --- work as usual. Fix tablet support<br>
* 3.0.0 alpha: January 6th --- Feature Freeze, tablet support + 1-2 stretch \
goals.<br> Priority features:<br>
* lazy brush (because it would add uniqueness)<br>
* Layer docker redesign.<br>
* multi-layer selection improvements<br>
* exporting to animated formats<br>
<br>
* 3.0.0 beta: February 3rd<br>
* 3.0.0 final: March 2nd<br>
<br>
## 3.1 Release schedule and contents<br>
<br>
* 3.1 --- 13th of April<br>
<br>
## 2.9 How many releases are left? 2.9.10, 2.9.11...<br>
<br>
* 2.9.10: December 2nd<br>
<br>
## 2.9 Animation. 2.9-based test releases for Windows and Linux (without \
translations).<br> <br>
Will be released 26th of November. See the checklist in the meeting notes.<br>
<br>
## Branching<br>
<br>
Branches:<br>
3.0 has the main branch for the feature frozen code<br>
3.0.1 tag that points to the released version<br>
If the released version was cancelled due to a blocker but, we branch into \
3.0.1.1 and cherry-pick neded commits there<br> <br>
<br>
# Coding Priorities<br>
<br>
For 3.0, Dmitry will work on tablet support, missing features for <br>
</blockquote>
animation, <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> multilayer handling, layer docker improvements. Scott will \
work on a design for the improved layer docker.<br> <br>
Missing animation features:<br>
<br>
* exporting frames to APNG/GIF/Spritesheet(This is a stretchgoal too)<br>
* cross-layer D&D<br>
* merging and other whole-image actions<br>
<br>
For 3.0, Boud is working on import/export of gimp brushes, general qt5 porting and \
now also on the OSX port...<br> <br>
Abrahams is creating new action system, therefore requests we take action related \
stretchgoals to him first for discussion. So when adding a feature and/or \
stretchgoal, please ask Abrahams about how to implement shortcuts<br> <br>
Abrahams has finished work on tablet support for Windows. We're back at a fork of \
the Qt code... But we'll try to keep the delta small so we can upstream patches \
to eCloud. For x11, that's hard since the tablet support <br> </blockquote>
is <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> all over the xcb qpa (Qt platform abstraction for the new \
X11 api).<br> <br>
## Vc 1.0 port<br>
<br>
Not much code needed, but let's push the change to a branch first so we can do a \
thorough regression test.<br> <br>
## 3.0 Tablet support<br>
<br>
<br>
Abrahams has finished work on tablet support for Windows. We're back at a fork of \
the Qt code... But we'll try to keep the delta small so we can upstream patches \
to eCloud. For x11, that's hard since the tablet support <br> </blockquote>
is <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> all over the xcb qpa (Qt platform abstraction for the new \
X11 api).<br> <br>
## A man from St. Petersburg wants to create a UIX design of tablet <br>
</blockquote>
interface <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> for Krita (no coding, just the design)<br>
<br>
This is a uni project, there might be some funding involved. Dmitry will <br>
</blockquote>
stay <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> in contact, this person's English is not great.<br>
<br>
## Documents on the wiki need a bit of love.<br>
<br>
* Dmitry make a mail about directory listing in wiki<br>
* Current manual writers will focus on userbase.<br>
* Scottyp is investigating mediawiki alternatives.<br>
<br>
# Sprint<br>
## Mini sprint in Q1, or a maxi sprint in Q2?<br>
<br>
Both, we'll have a sprintlet in Deventer with at least Dmitry in February. \
Everyone else is welcome, but there might not be funding for a lot of <br> \
</blockquote> travel!<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <br>
Boud will contac the e.V. board about a KDE sponsored big sprint in Q2.<br>
<br>
-- <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> \
_______________________________________________<br> Krita mailing list<br>
<a href="mailto:kimageshop@kde.org" target="_blank">kimageshop@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kimageshop" rel="noreferrer" \
target="_blank">https://mail.kde.org/mailman/listinfo/kimageshop</a><br> <br>
</blockquote>
_______________________________________________<br>
Krita mailing list<br>
<a href="mailto:kimageshop@kde.org" target="_blank">kimageshop@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kimageshop" rel="noreferrer" \
target="_blank">https://mail.kde.org/mailman/listinfo/kimageshop</a><br> <br>
</blockquote>
_______________________________________________<br>
Krita mailing list<br>
<a href="mailto:kimageshop@kde.org" target="_blank">kimageshop@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kimageshop" rel="noreferrer" \
target="_blank">https://mail.kde.org/mailman/listinfo/kimageshop</a><br> \
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div \
class="gmail_signature">Dmitry Kazakov</div> </div>
[Attachment #6 (text/plain)]
_______________________________________________
Krita mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic