Comments on: KOffice 2.2 Release Schedule http://blog.cberger.net/2009/12/03/koffice-2-2-release-schedule/ What I do, where I live, what I think. Sat, 17 Dec 2011 20:16:30 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Cyrille Berger http://blog.cberger.net/2009/12/03/koffice-2-2-release-schedule/comment-page-1/#comment-339 Cyrille Berger Thu, 03 Dec 2009 15:25:25 +0000 http://blog.cberger.net/?p=889#comment-339 I share your concern. What we will do (and apparently Qt does to) is to have an unstable branch where features are merged regulary for early testing. And once the feature got sufficient testing in that unstable branch it is move to the stable branch. I share your concern. What we will do (and apparently Qt does to) is to have an unstable branch where features are merged regulary for early testing. And once the feature got sufficient testing in that unstable branch it is move to the stable branch.

]]> By: dont like http://blog.cberger.net/2009/12/03/koffice-2-2-release-schedule/comment-page-1/#comment-338 dont like Thu, 03 Dec 2009 15:14:19 +0000 http://blog.cberger.net/?p=889#comment-338 Hello, my 2 cents for the "trunk is always stable" trend, i dont like it because, what you get is, development gets away from the community, and i made in private git trees. this is good for stability, but not good community wise.. okay, i think its good when trunk is stable, but i also want to help with the bleeding edge... please find a good time, when you sync features - and dont sync them only when they are finished ... Hello,

my 2 cents for the “trunk is always stable” trend, i dont like it because, what you get is, development gets away from the community, and i made in private git trees. this is good for stability, but not good community wise..

okay, i think its good when trunk is stable, but i also want to help with the bleeding edge…

please find a good time, when you sync features – and dont sync them only when they are finished …

]]>