From kde-core-devel Wed May 14 00:36:42 2003 From: Daniel Stone Date: Wed, 14 May 2003 00:36:42 +0000 To: kde-core-devel Subject: Re: KDE 3.2 release cycle X-MARC-Message: https://marc.info/?l=kde-core-devel&m=105288796701554 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--H4SyuGOnfnj3aJqJ" --H4SyuGOnfnj3aJqJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 13, 2003 at 03:37:22PM -0600, Aaron J. Seigo wrote: > On Sunday 11 May 2003 09:19, George Staikos wrote: > > Doing a release is not small undertaking. It is a lot of work for t= he > > packagers, the release coordinator(s), the translators, the documentati= on > > team, and developers. >=20 > CVS snapshots meant as preview releases for developers/enthusiasts do not= need=20 > to go through the motions of actual releases. translations don't need to = be=20 > up to snuff, nor does documentation. >=20 > a set of tarballs that are the result of a cvs export && make -f Makefile= .cvs=20 > should suffice... for that matter, a release of konstruct that is set up = to=20 > grab a CVS version would probably be enough... if people could do this: >=20 > tar jxvf kdesnapshot.tar.bz2 && cd kdesnapshot/meta/everything && make in= stall The problem there is that, no matter how much you distance it from a release, people will always still get the impression that you're supporting it as an official release. Negative feedback sticks a lot more than positive feedback. All it takes is a couple of people whining about how it sucks and how unstable it is to scare off a lot of people. > and get a working kde CVS snapshot, that would be awesome... in fact, one= =20 > would imagine that it would be possible to write a simple script that=20 > automatically cvs export's a set of KDE tarballs and uploads them to a we= ll=20 > known server so that releasing a new snapshot is the matter of running a= =20 > single command ...=20 Can you point to a single day where everything has just *worked* in CVS? > > KDE becomes more complex with each release, and each > > release requires more work to test and polish. HEAD is definitely not > > stable yet, and there are major unresolved issues. 3.1.x, however, is > > quite stable and making sure that the it receives regular bugfixes is a > > good way to provide users who don't use CVS-HEAD. >=20 > this isn't about providing users, it's about providing enthusiasts and=20 > developers who wish to keep up with KDE development. these are important= =20 > members of our community. Why can't they just do for i in qt-copy arts kdelibs kdebase kdeadmin kdebindings [...]; do cvs -z4 co $i; done? I don't see the difference, except a lot more pain for us. --=20 Daniel Stone KDE: Konquering a desktop near you - http://www.kde.org --H4SyuGOnfnj3aJqJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+wY+acPClnTztfv0RAruRAJ9b1PwLmYa6kUnD7WUOOu6nM2je7wCfY3PV cRmnWTJyd0AKOS6eiDwYzPk= =I6Ck -----END PGP SIGNATURE----- --H4SyuGOnfnj3aJqJ--