Moving 3.5 development into branches/KDE/3.5

[Maksim Orlovich]

> to make PIM development productive is to not require us to fiddle with
> moving
> targets (qt 4/kdelibs 4), bc issues, merging and all other related
 stuff.

On the flip side, this means you'll likely have to port to kdelibs that
look very different from current ones, rather than porting in stages. Pick
your poison.

>
> Either that, or throwing in more manpower to do the 'real' work. Dealing
> with
> merging is just wasting *very* precious time.

Which is why people can't reasonably expect the very few people on KDE4
porting team to keep up with the 3.5 development all on their own.