KDE 3.2 release cycle

[Aaron J. Seigo]

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

On Wednesday 14 May 2003 03:18, Stephan Kulow wrote:
> On Tuesday 13 May 2003 23:37, Aaron J. Seigo wrote:
> > and get a working kde CVS snapshot, that would be awesome... in fact, one
> > would imagine that it would be possible to write a simple script that
> > automatically cvs export's a set of KDE tarballs and uploads them to a
> > well known server so that releasing a new snapshot is the matter of
> > running a single command ...
>
> You're not serious, aren't you?
> Look through the file list of ftp://ftp.kde.org/pub/kde - the word
> "snapshots" has been in there since ~1997

it's great that they are available and that their creation is automated, but 
there are two challenges with ftp.kde.org/pub/kde/snapshots as i see it:

 o there is no coordination as to when they are to be tagged. when a person 
downloads those tarballs, they get recent CVS: broken or not. this makes them 
worthless as preview releases, which should offer at least a modicum of 
stability. they wouldn't require the QA / testing that an actual release or 
even an alpha release gets, but they should be tagged around times when CVS 
"feels" healthy (fewer crashes, motr new complete features, etc).

 o they aren't publicized. Mosfet's original concern, as i read  it, was that 
if the "KDE fan" part of our user base was left without visible signs of life 
and/or something new to play with every few months while we extend a release 
cycle, they won't be very happy and may decide that KDE development is 
slowing up or even stopping.  this would be a job for kde-promo.

the build script in there is ok, but something like konstruct would probably 
be more useful, as it takes care of the downloading as well as the building 
and installing... and since these are "might kill your firstborn if you use 
it" type releases, it should be installed in the home directory.

obviously, this is all a moot point if we don't have longer release schedules.

- -- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE: The 'K' is for 'kick ass'
http://www.kde.org       http://promo.kde.org/3.1/feature_guide.php
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+wg8x1rcusafx20MRAstwAJ9ifc24mAXRS7IitE9osr8rxPRyNQCdHOks
wVKX6rJ/JFb0PX96B4KrOm0=
=0SL9
-----END PGP SIGNATURE-----