“Tom and Aaron discuss timing and release schedules, and
development cycles. Aaron talks about trunk/ and freezes therein
should follow a natural lifecycle. This assumes that the whole KDE
community lives and breathes as one individual, synchronised and
all. So a development-and-release-cycle forces all developers into
one rhythm. Everyone has to follow this one release rhythm. It’s a
good idea, but I think we should also make the lives of those
easier that choose another breathing ryhthm. There are a couple of
things to consider here. The most obvious being that we need this
flexibility anyway. We rely on certain release mechanisms and
interface stability policies in other projects as well. (We partly
solve this problem by providing abstraction layers, think phonon
and solid). Now the interesting case is that Phonon, which is new
in Qt’s 4.4 release is also provided by Qt. Phonon now breathes in
a 9 month release cycle in Qt, and a 6 months one in KDE. So one
could argue that it’s a smart idea to breathe in the same rhythm as
Qt does. We could follow up every release of Qt with a KDE
release…”