From kde-release-team Wed Nov 28 16:27:43 2007 From: "Aaron J. Seigo" Date: Wed, 28 Nov 2007 16:27:43 +0000 To: kde-release-team Subject: Re: Delaying 4.0? Message-Id: <200711280927.43574.aseigo () kde ! org> X-MARC-Message: https://marc.info/?l=kde-release-team&m=119626730317647 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============0596621093==" --===============0596621093== Content-Type: multipart/signed; boundary="nextPart99694647.Xp9Irtu7BK"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart99694647.Xp9Irtu7BK Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 28 November 2007, Andras Mantia wrote: > 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? =C2=A0Not I. > > No, I don't, but this is shows clearly how bad is to do a time based > release for a *new* product. that's why we didn't. we gave ourselves 2 years and really free floating=20 schedules.=20 there is, however, a difference between not doing a time based release and= =20 never releasing. > Sure, we have to draw a line and say this=20 > is the release time, because otherwise we will never stop adding new > features.=20 exactly. > 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 > shouldn't be any reason (like now the party) that will force us to > release something broken. you're presenting two scenarios as if they were the only ones. they aren't. the fact is that people are already working on new features (see Raphael's= =20 work on the file dialog for instance) and asking for branches and what not.= =20 we can't hold on to a freeze forever. we need to release. our users need to get a release. our 3rd party application developers need to get a release. etc... hell, WE need to get a release to get this behind us and our wheels moving= =20 again. because everytime i feel we get traction here, someone manages to po= ke=20 their head up and say, "OMG! we can't release now!" and everyone goes back = to=20 a happy slow pace. screw that. > Of course, like others, I still hope KDE 4.0 will be in a good enough > shape at that time, but if not, I'd rather not release it before the > party. i hear and respect your opinion. i disagree with it (people naturally tend = to=20 have various opinions =3D), but it does highlight that we need a certain "g= ood=20 enough"ness to the release to make people such as youreself to be satisfied= =2E=20 i truly hope that you help make things as good enough as possible while als= o=20 communicating *clearly* and *constructively* what "good enough" means. vagu= e=20 hand waving statements are not enough information to help me (and i assume= =20 others) help meet our combined expectations. this isn't the list for that conversation, though. we can take it elsewhere= =2E=20 perhaps in the blogosphere? > You can still celebrate the "upcoming KDE 4.0" release there. ;)=20 this is why promo people don't tell us how to code. it would come out like= =20 crap. =2D-=20 Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Trolltech --nextPart99694647.Xp9Irtu7BK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBHTZb/1rcusafx20MRAtzzAJ9U2T8EcQ+0CVahIIG26hU4JDckYQCdEzgy fngihfvMTAy2FHrWlJNCmOA= =lT/A -----END PGP SIGNATURE----- --nextPart99694647.Xp9Irtu7BK-- --===============0596621093== 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 --===============0596621093==--