[prev in list] [next in list] [prev in thread] [next in thread] 

List:       calligra-devel
Subject:    Re: next release and release pace in general
From:       Boudewijn Rempt <boud () valdyas ! org>
Date:       2013-01-23 18:59:43
Message-ID: 201301231959.43941.boud () valdyas ! org
[Download RAW message or body]

Well, I'm kinda torn about this... I do want to get the latest features and fixes in \
people's hands as soon as possible. It's rather weird that the most intense users of \
Krita build master on a daily basis just to get that -- releasing more often might \
save them time (though it would cost us testers). But users really deserve the stuff \
we do as quickly as possible: that's why we work on those things! It is already \
getting old that I have to explain to people that the smoothed painting is done, but \
won't be in the 2.6 release, but 2.7...

For Windows, once I got that setup working again, I'll probably just publish regular \
git master builds. Those are more stable than any release anyway, or should be!

On the other hand, an open source project has only one moment when it can create \
noise, buzz and publicity, and that's on a release. I'm personally not capable of \
doing that properly every four months -- that's why I didn't do much for the 2.5 \
release. Although that had other reasons, too -- family resons. For 2.6 I'm working \
really hard on another splash. I think I spend about 40 hours on krita release \
announcements and publicity, if I spend time on it at all.

So, I'm torn. I cannot manage to create a buzz around krita every four months, and \
Krita still needs lots of buzz. I also cannot square it with my conscience to keep \
fixes and features from users for longer than strictly necessary.

I haven't got a solution...

-- 
Boudewijn Rempt
http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl
_______________________________________________
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel


[prev in list] [next in list] [prev in thread] [next in thread]