Work on kde4/kdelibs branch

[Thiago Macieira]

Caleb Tennis wrote:
>So I'm in the mist of a port of one of our company's applications to Qt4
> and am in need of some classes in kdelibs as well.  What's the policy
> on commits to the kde4/kdelibs branch?  Is it just to make it work with
> Qt4 or are cleanups and BIC changes allowed as well?  There are some
> classes I'd like to wean off of QT3SUPPORT but it may break things in
> the process outside of kdelibs, and I don't want to upset people trying
> to work in the other directories of that branch.

Hello Caleb,

The work on the branch is going at a bit slow pace. We have some people 
really dedicated to making it compile and even work, somtimes removing 
the Qt3Support code. So, yes, you are welcome to work on the code.

But we're avoiding big changes as of now. The reason for that is that 
trunk is still Qt3-based and will become KDE 3.5. So we're merging back 
the changes done to trunk (every 1000 revisions or so). This means big 
code cleanups are not easy to merge, neither for the library nor the 
application. In fact, some applications asked not to join the KDE4-port 
effort because of this reason: they are still changing rapidly in trunk.

We should go full steam in the port as soon as KDE 3.5 is released, which 
I expect to be in a couple of months' time.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

3. Ac seo woruld wearð geborod, swá se Scieppend cwæð "Gewurde Unix" and 
wundor fremede and him "Unix" genemned, þæt is se rihtendgesamnung.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050708/78419ff4/attachment.sig>