there are classes in kdelibs that sill need to get some love in prep for 4.0. a lot of that is pretty basic stuff, such as:
- figuring out what to do with kdelibs/kdeui/klanguagebutton.cpp
- tracking down abuses of bools in the API (hello KIO::NetAccess!) and replacing them with enumerations for readable code
- making sure no classes have any data members other than the Private* dptr in the public interface
- getting rid of any inlined methods in public interfaces
some of it isn't as trivial, such as:
- finishing out changes to kconfig (i know of two sets of work going on there)
- going over and essentially rewriting large parts of the kde file dialog so it uses qt4/kde4 properly
- icon loader improvements (so that app devs, such as the amarokers, can rest easily knowing their icons are going to look nice without screwing over those using comprehensive icon sets in the process)
- oxygen style
- knewstuff2? (plasmagik will be shipping with plasma for 4.0)
- ... other stuff people are working on ;)
the list is shorter than it was, but it's still longer than short. hopefully we'll punt on as little of this as possible, but i feel it is inevitable some will as it is simply not possible to have everything one could dream of in a given release. there are things that can be added or fixed post-4.0 and so isn't a big deal. and things like nepomuk, even if they do make it in for 4.0 (and that's not a requirement at this point), still won't fully see their potential realized for a few releases as applications tool up to use the new goodies. it'll also take the serious usage that only a stable release sees to really get solid, phonon, decibel, et al to the point of being able to take them for granted much as we do now with many of the technologies that debuted with kde 2.0.
but yeah ... lots of work ahead between now and akademy.