Releases in 3 months

Scott Kitterman kde at kitterman.com
Mon Jul 8 15:40:21 BST 2013


On Monday, July 08, 2013 04:35:30 PM Àlex Fiestas wrote:
> On Monday 08 July 2013 16:26:00 laurent Montel wrote:
> > No it’s not a good idea because nobody tests branch you can see pb that we
> > had when we merge akonadi branch (last big changes).
> > So no develop in branch will just create more bugs.
> > 
> > And same question: why reduce time by 2 ?
> > 
> > What we will have as result ? Ok in january with will release 4.14 great,
> > so it’s right we will never release a so big number of kde but don’t know
> > if it’s a good idea to run after number...
> > 
> > And when we reduce time for example for 4.12 which finish in october, for
> > me for example I have 2 weeks of vacations => dev == 1 month 1/2 ! Great
> > for create features...
> 
> Then you can target your features for January (4.13) there is no pressure.
> As I said before you can keep having 6 months schedule while others like
> Frank (or myself) can release features based on 3 month schedule.
> 
> You don't have to change the way you work because of this.

We've already experienced having some parts of the SC skip releases and it was 
a real problem from a distribution perspective.  Please, let's not do it 
again.

Scott K




More information about the kde-core-devel mailing list