From kde-devel  Thu Jun 09 20:35:52 2011
From: "Andreas K. Huettel" <dilfridge () gentoo ! org>
Date: Thu, 09 Jun 2011 20:35:52 +0000
To: kde-devel
Subject: Re: No more release schedules.
Message-Id: <201106092235.58555.dilfridge () gentoo ! org>
X-MARC-Message: https://marc.info/?l=kde-devel&m=130768183121110
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1728823338=="

--===============1728823338==
Content-Type: multipart/signed;
  boundary="nextPart3534336.ZlBGp9DEGm";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart3534336.ZlBGp9DEGm
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Dear KDE upstream,

> Since KDE is the community, how can we do a KDE 4.8? And then Platform wi=
ll
> call itself 5 if I understood correctly. So how do we call a new release
> schedule then?

I just read a very good novel where all such talk about "Software Collectio=
n"=20
or "Platform" was aptly called "commercial bulshytt". I think many of us,=20
including your "only-users", would appreciate it if you all there upstream=
=20
would just stick to KDE, because that is what everyone uses. Nothing else.

> > Are you serious that you want to decouple the release of our
> > frameworks from
> > each other? THat would create a huge mess, extreme amounts of
> > overhead, be
> > very destructive to our community... This puzzles me as I know how
> > much you
> > love KDE.
>=20
> What does my love for KDE have to do with it? I think it's good for KDE to
> let each module set their freezes on their own, depending on which work
> flow they will adapt. If we decide it early the module maintainers have
> time enough to get used to creating the schedule.

Basically this is nothing but a dissolution of the KDE project as a whole.=
=20
Sure, we'll end up with a lot of projects using and enhancing kdelibs (or=20
whatever becomes of that), but there will be no coherence anymore.

> We can set a preferred release day twice a year, which every module can
> work to if they like.
> We can still package and release them if you like, that's independent of
> the schedules.

That both makes no sense. Suggestion 1 fails completely with the "if they=20
like" part, since we all know already how much pain the "out of sync kdepim=
"=20
caused. Suggestion 2 fails with the "independent of the schedules" part,=20
because you can't release somthing that is not stabilized and tested.

Please try to get some sense back...

Cheers,=20
Andreas

=2D-=20

Andreas K. Huettel
Gentoo Linux developer=20
dilfridge@gentoo.org
http://www.akhuettel.de/

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

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

iEYEABECAAYFAk3xLq4ACgkQ3ao2Zwy3NWoptQCdEEf475/PxEaj+ODnETTg5LKs
2NcAoI1HcFXnd78+MdPH3IqU6ZOXjSnb
=3C7V
-----END PGP SIGNATURE-----

--nextPart3534336.ZlBGp9DEGm--

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

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============1728823338==--