From kde-core-devel  Mon May 30 22:50:26 2005
From: Ingo =?utf-8?q?Kl=C3=B6cker?= <kloecker () kde ! org>
Date: Mon, 30 May 2005 22:50:26 +0000
To: kde-core-devel
Subject: Re: Moving 3.5 development into branches/KDE/3.5
Message-Id: <200505310050.27208 () erwin ! ingo-kloecker ! de>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=111749378314063
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1626232.x151WorEOX"

--nextPart1626232.x151WorEOX
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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=20
from 3.5 to trunk a PITA. Note that I reserve the right to revert any=20
changes in trunk/KDE/kdepim/kmail which thwart our efforts to keep life=20
easy for us.

Regards,
Ingo

--nextPart1626232.x151WorEOX
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCm5izGnR+RTDgudgRAtGAAJ4tgD/B3P//8yK7EuXdPHflXWIJtACePSQv
gyj+2d9ukxhEI6FIthD7T9k=
=RcsM
-----END PGP SIGNATURE-----

--nextPart1626232.x151WorEOX--