AUG
26
2003

State of HEAD

Submitted by dkite

I am thinking of adding a feature each week describing the state of CVS HEAD. I will report which modules build, which don't, and any glaring bugs or neat stuff. My usage pattern is pretty typical, ie. email, browsing, addressbook, etc.

I have hesitated for two reasons; a lack of time. Also a stable bug-free development branch is a non sequitur.

But with the feature freeze the situation is changed. The state of the body of code is of interest.

Any objections? The purpose isn't to berate or complain, simply to report.

Derek

Comments

Hi,

would be nice if you could pick a "bug of the week" in your series that people can jump on. I did something similar on kde-core during 2.2 development and usually those things got fixed quite soon to get rid of the most annoying bugs for every day usage of HEAD.

By KDE User at Tue, 08/26/2003 - 10:03

Well, I suspect it will happen as you describe. Frankly that is why I hesitate. Seeing what happened with the clock dialog, and after the screenshots I did a while ago, I don't want to create a flurry of wasted activity around the things I bring up.

Derek

By dkite at Tue, 08/26/2003 - 19:41

I suppose you could take the bug with the most votes in Bugzilla and make it the Bug of the Week. You could then have a reigning champion or something along those lines. Anyways, just my silly idea. ;)

By mattr at Wed, 08/27/2003 - 03:17

> I will report which modules build, which don’t, and any glaring bugs or neat stuff.

Great.. sorta like Mozilla has with it's tinderbox.

By KDE User at Tue, 08/26/2003 - 13:39

being fundamentally lazy, do you have a link?

Derek

By dkite at Tue, 08/26/2003 - 19:38

http://www.mozilla.org/tinderbox.html

By Na at Wed, 08/27/2003 - 21:05

I think it would be a good idea.

By KDE User at Tue, 08/26/2003 - 18:50

Well, I am starting to test KDE cvs too.
I am also making mandrake rpms for it, since compiling rpms is a safe way no to destroy your sistem. (You first compile it, then you install it. And if something is wrong, you can retur your system fo the state it was.

I managed to build arts, kdelibs, kdebase, kdenetwork, kdesdk, kdeutils, kdeartwork. They all work.
I could not manage to compile KDE pim the last three days. I will try it again tomorrow.
As soon as U have a more or less stable set of rpm, i will make it available. This rpms will not integrate with mandrake at all. But they will be safe and have independent configurations.

cwoelz

By KDE User at Tue, 08/26/2003 - 20:44

Ralf Nolden did this in KDE 2.x times and it was pretty useful, I certainly wouldn't object.

e.g.

http://lists.kde.org/?l=kde-core-devel&w=2&r=1&s=cvs+issues+week+nolden&q=b

By Chris Howells at Wed, 08/27/2003 - 11:46

> I will report which modules build, which don’t

Usually if a module doesn't build it's only for some hours.

By KDE User at Thu, 08/28/2003 - 07:13