Moving 3.5 development into branches/KDE/3.5

[Ingo Klöcker]

On Monday 30 May 2005 22:51, Stephan Kulow wrote:
> Am Montag 30 Mai 2005 21:43 schrieb Martijn Klingens:
> > On Monday 30 May 2005 21:21, Stephan Kulow wrote:
> > > This is a change of policy and was the initial goal. The kde4
> > > work branch was just temporary. The main difference to the
> > > current situation is:
> > >
> > > * KDE4 is the main target, KDE 3.5 development is defined as
> > > backport
> >
> > This collides for the roadmap of KDEPIM that we decided on last
> > weekend during the KDEPIM development meeting. KDE 3.5 will be the
> > main target until early august for PIM and basically nobody will be
> > working on KDE 4 yet. We simply lack the manpower to work on two
> > targets, so KDE 4 will have to wait.
>
> I'm fine with kdepim developers working on KDE 3.5, but not in trunk
> and every 3.5 commit has to be merged in trunk. I hope it's possible
> in one way or the other.

Only if nobody starts to mess around in trunk/KDE/kdepim making merging 
from 3.5 to trunk a PITA. Note that I reserve the right to revert any 
changes in trunk/KDE/kdepim/kmail which thwart our efforts to keep life 
easy for us.

Regards,
Ingo
-------------- 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/20050531/54e58790/attachment.sig>