[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: 2.2 RELEASE SCHEDULE (proposal) [NOTE: 2.2 != 2.1.1]
From:       Jason Stephenson <panda () mis ! net>
Date:       2001-03-03 16:53:45
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Umm, actualy, I've been thinking the same thing as Dalwit on this topic. 
IMHO, the release schedules are too tight. In fact, they're worse than some I 
suffered under working at my previous job, and I got fired 'cause I 
complained too vehemently about the schedule on the last job.

Dalwit is right. If we're adding functionality to applications in the 2.2 
release, then if we don't want it to be full of bugs, then maybe we should 
push the beta release back a month or so? I understand all about release 
earlier, release often, but at some point you alienate your users, 
particularly if you don't have time to write decent code. Pushing the 
releases back gives all of us some time to breathe and gives our users a 
chance to get used to the features in 2.1 as well as anticipate the 
improvements in 2.2! We don't want people running older version of KDE all 
the time, do we? I mean, I've got CVS access, and I'm still running 2.0.1!

Anyway just my thoughts on the matter.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjqhIZoACgkQRZu1ZcECWs3HggCgm3Vzl7hkyaVZ4azltA+mST0r
8fYAn1BPckv7iG5EOJp/S5JcSh53y1vJ
=sjAu
-----END PGP SIGNATURE-----
 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]