--===============0838881025==
Content-Type: multipart/signed; boundary="nextPart1298359.durYKvTTI1";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1298359.durYKvTTI1
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

On Friday 29 August 2008 01:23:41 Allen Winter wrote:
> On Monday 25 August 2008 08:51:35 Stephan Kulow wrote:
> > Am Montag 25 August 2008 schrieb Allen Winter:
> > > On Monday 25 August 2008 08:35:02 Stephan Kulow wrote:
> > > > Am Montag 25 August 2008 schrieb Aaron J. Seigo:
> > > > > while it might be "best" to have everyone's hands on KDE4, it's
> > > > > also realistic that there will be those who remain interested in
> > > > > KDE3 for various reasons and there's no reason to try and control
> > > > > that beyond encouraging KDE4 to be the primary focus. as it alrea=
dy
> > > > > is for virtually
> > > >
> > > > Actually I think the best way to let people focus on KDE4 is making
> > > > sure KDE3 becomes unusable as stable platform in allowing untested
> > > > experiments.
> > >
> > > At least I'm sure that KDAB tests kdepim changes and is around
> > > to help fix and port stuff.  So people who need kdepim 3.5 could
> > > conceivably switch to the kdepim/enterprise branch.
> >
> > I don't have an issue with kdepim 3.5.17 being released. But I do have
> > one with kdelibs or kdebase changes based on experiments. And actually
> > kdepim was one of the modules I had to fix up before it would compile.
>
> The responsible parties will be flogged :)
> Sorry.
>
> BTW, I am with Stephan on the EOL 3.5 issue.
> We simply can't be throwing untested code over the wall at the 3.5 branch
> and hope that it works.  We've already encountered 2 evil bugs caused
> by such code in kdepim 3.5.10.
>
> If some "entity" wants to take up real development responsibility for
> 3.5.x, then have at it.  But that's not for me.  We have far more work th=
an
> we can possibly do in a lifetime in kdepim as it is.
>
> I expect KDAB will continue doing the best they can for kdepim enterprise.
> But the rest of the kdepim team will be moving onto KDE 4 and I plan
> to tightly monitor the kdepim 3.5 branch and stop anything but the most
> obvious bug fixes there.
>
> IOW: branches/KDE/3.5/kdepim is essentially frozen.

=46or the record: I completely agree with Allen here, let's stop committing=
 to=20
that branch.
As Allen already mentioned, nobody tested it and some commits caused=20
regressions like bug 169991.

Regards,
Thomas

--nextPart1298359.durYKvTTI1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQBIuruFKglv3sO8a1MRAvAqAKCYqMkgShHcilkexuyqc2UWq2B5WwCfeERb
Uw09k4KnFFuf7oKH1eraRZk=
=E09T
-----END PGP SIGNATURE-----

--nextPart1298359.durYKvTTI1--

--===============0838881025==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
--===============0838881025==--