Setting a kdelibs Freeze Date
Harri Porten
porten at froglogic.com
Fri Jun 15 19:58:18 BST 2007
On Fri, 15 Jun 2007, Tom Albers wrote:
> Op vr 15 jun 2007 19:40 schreef u:
>> I think it would be really cool if we could use the "coding marathon" on
>> akademy as an opportunity to do one last review session for kdelibs. Allowing
>> making those last BI changes would be rather helpful for that meeting. So
>> pushing it by two weeks (to July 9th) would let us do those cleanups while
>> sitting face-to-face, which tends to be pretty helpful.
>
> That would mean the application developers will be constantly
> recompiling kdelibs during akademy instead of coding. Whatever we decide
> one group will not be happy.
Libraries developers without users can't be happy either. And that what
happens if we do not stop to "clean up" the API now. There are zillions of
deprecated and todo warnings when compiling KDE so I think finishing the
*implementation* (adding missing parts, fixing bugs) is much more
important than perfectionizing an API that will be obsolete a month after
its final release because Qt 5 comes out.
Harri.
More information about the kde-core-devel
mailing list