--===============1208746647== Content-Type: multipart/signed; boundary="nextPart1847784.svjY5AWdg9"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart1847784.svjY5AWdg9 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 28 November 2007, Rex Dieter wrote: > So, do *you* want to be the one to tell the event organizers that all > their hard work and effort to pull the event together is now in > jeopardy? =A0Not I. No, I don't, but this is shows clearly how bad is to do a time based=20 release for a *new* product. Sure, we have to draw a line and say this=20 is the release time, because otherwise we will never stop adding new=20 features. Yet, if the release time is close and there are clear signs=20 that the quality for the product is not up to our expectations, there=20 shouldn't be any reason (like now the party) that will force us to=20 release something broken. Of course, like others, I still hope KDE 4.0 will be in a good enough=20 shape at that time, but if not, I'd rather not release it before the=20 party. You can still celebrate the "upcoming KDE 4.0" release there. ;) Andras =2D-=20 Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org --nextPart1847784.svjY5AWdg9 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) iD8DBQBHTW+2TQdfac6L/08RAuTCAKCV4CftC1MmEIDPr4u4bdJ0g04mjQCfSlOY 3OXiWX4MiSlsProLvh+3mFI= =TsoR -----END PGP SIGNATURE----- --nextPart1847784.svjY5AWdg9-- --===============1208746647== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team --===============1208746647==--