On 2013-07-29 19:57, Dmitry Kazakov wrote:
1) Our master is currently in releasable state, which is exactly what
we wanted to achieve a couple of sprints before. I think we shouldn't
drop this achievement. I should admit that many painters use the
script by David, which also depends on master branch. It might be not
very easy to explain all the people to switch branches while using the
script (yeah, we have such experience with compiling Vc 0.7). With
breaking master by the porting work, Krita Lime releases will not be
possible anymore. At least we will need a special branch for backports
and we will have to maintain it, which is hardly possible.
Well porting to Qt5/KF5 is one of those time when you want to break the
"master is always releasable and always open for merges" rule.
Irrespectively of whether you want to do it now or later. For two
reasons:
1) the qt5-branch will be diverging quiet a bit from master, making it
difficult and time consuming to merge, meaning that a lot of effort will
be lost on keeping qt5-branch up-to-date with what is on master
2) it is a good idea to have as many developers as possible involved in
helping with the port
As for the problem of users using master, you have two alternatives:
* tell them to not update
* freeze "master" (as in no commits, except for compile fix) and then
use a different branch name for porting. After all "master" is just an
other branch.
--
Cyrille Berger Skott
_______________________________________________
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
