next release and release pace in general

[Jaroslaw Staniek]

On 23 January 2013 12:05, C. Boemann <cbo at boemann.dk> wrote:
> Hi
>
> I'm worried about our release pace. For 2.6 Words was able to make exactly 0
> new features. Sure we made several fixes, but apart from a few strings those
> could (almost) just as well have gone into a bugfix release.
>
> I'm also worried that even though we do manage to put in an occasional new
> feature, we don't make good enough PR out of it, simply because every release
> contains so few new things that people miss the big picture. I think Amarok
> has released new features over the last few years but because they do like we
> do, I'm not at all sure they even released.
>
> What I'm saying is that I think we are not making a big enough splash.
>
> And I'm also saying that personally I feel like I've been in a constant
> release mode, fixing bugs, since our first release. Now bug fixes are needed for
> sure and I also like that we are stabilizing. Don't get me wrong here.
>
> But hacking should also be about having fun and having time to make new stuff.
>
> Personally I think we should go back to release when we have enough to make a
> splash. That can be 2 months or 9 months. It will vary.

I am with you here. But it will be different depending what apps we're
talking about.
Going together as Calligra has advantages of being a big sum,
comprehensiveness, shared frameworks, PR, and so on. But when it comes
to schedules we depend on consensus.

Every single application has different major use cases picked by given
maintainer, different priority. This is a Good Thing[tm].

So I am hoping for finally implementing means for constant
updates/releases: 1. emphasizing support for distros with constant
releases (this includes our "own" releases of Windows and Mac), 2.
starting something like http://kdesrc-build.kde.org, 3. enriching GHNS
infrastructure for extensions, like in https://addons.mozilla.org and
for templates (that all requires increases support for noarch through
scripting and theming)

I would also not forget that for some developers, working on given
frameworks themselves can be great fun. It is at least for me.

> I still think we should have always summer in master and that we never litter master with half
> baked features, so we are always ready to branch out.

+1 as always

-- 
regards / pozdrawiam, Jaroslaw Staniek
 Kexi & Calligra & KDE | http://calligra.org/kexi | http://kde.org
 Qt Certified Specialist | http://qt-project.org
 http://www.linkedin.com/in/jstaniek