KDE 4.1 planning

[Sebastian Kügler]

On Tuesday 08 January 2008 02:14:02 Matt Rogers wrote:
> Why exactly do the distros matter when planning our releases? (I know
> I've asked this and it's been explained before, but I still don't get
> it. Perhaps I never will.) 

Distros are the ones that get our software to the user. KDE is a 'raw' 
product, we need the distros' integration work (adding an OS, that kind of 
details ;-)),

There's a mutual dependency between us and the distros, we need them to get to 
software shipped for users, they need us because we provide raw material for 
their finished 'product'. Aligning schedules makes it easier for distros to 
ship new products based on new KDE versions.

> If you're just proposing a 6 month release 
> schedule because that's what the distros do, well, then that's a load
> of bunk, IMHO. If you're proposing a 6 month release schedule because
> you think it provides good sustainable pace for the majority of us,
> then that's an actual reason.

Both applies. A 6 month cycle makes it easier to get our software also to our 
fellow developers. The KDE4 platform is in pretty good shape, so we probably 
don't need too much integration work (in the range of 8 - 6 weeks to settle 
down a 4.x). We will be building software on top of that, and not change the 
underlying system too much (so that we need lots of time before the code is 
releasable again). That gives us a good 4 months from release to next feature 
freeze. For larger changes, it basically means: "Work in a branch until you 
can get your code stabilised within 2 (worst case) to 6 (best case) months." 
That sounds reasonable to me.

6 months also keeps the amount of changes surmountable. With a stable basis, 
we can release more often, so the integration work (fixes in A with features 
in B to work together seamlessly) is done more 'in the process'. Less 
powerplanting, which I think is good.
-- 
sebas

 http://www.kde.org | http://vizZzion.org |  GPG Key ID: 9119 0EF9 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 481 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/release-team/attachments/20080108/8b873b1e/attachment.pgp