[RFC] KConfig merge

[Matthias Kretz]

On Wednesday 03 October 2007, Tom Albers wrote:
> At Wednesday 03 October 2007 04:47, you wrote:
> > For those reasons, I would like to ask for an exception form the API
> > freeze for this patch, especially as this can't be done later in a BIC
> > way.
>
> Beta 3 is not even tagged and you request to make BIC changes to it?

Asking such a question before tagging is better than after, no?

Regarding the question my opinion is that:
1) KConfig is really in need of cleanup. I have not looked at the actual patch 
yet, but everything that improves it is welcome.
2) Such a big change will introduce new bugs. Either porting errors or bugs in 
the implementation of the changed interfaces. The worst thing about it is 
that it might hold up other parts of the KDE4 desktop that need all the time 
they have to get their stuff ready.

To find a compromise, what I would like to see is complete branch of trunk/KDE 
that is ported to the KConfig cleanup and "proven" to work correctly. 
Where "proven" means that as much regression testing as possible was done 
(now if we only had more unit tests...)

What this means for tags and releases I don't know.

-- 
________________________________________________________
Matthias Kretz (Germany)                            <><
http://Vir.homelinux.org/
MatthiasKretz at gmx.net, kretz at kde.org,
Matthias.Kretz at urz.uni-heidelberg.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071003/0ac3b080/attachment.sig>