KDevelop gets more templates, Quanta
gets better action toolbars and Umbrello gets new code generators. A dummy KDE 3.2 release schedule. More merges from Safari to KHTML.
Plus a large number of bug fixes. Read it all in the latest KDE-CVS-Digest.
Personally I envisaged a Crystalised version of the "K" rather than a gear.... I note that dot.kde.org and the cvs-digest are using very slightly different gears at the moment.
I'm happy to change the kde.org favicon.ico to a gear though, but I can't quite decide if I like the dot one or cvs digest one more at the moment.
Out of curiosity, but why don't you use ChangeLogs as any other project ? So everyone could look on their own what's changed. Many ChangeLogs in the kde modules are outdated for years or some projects simply don't have any.
Changelogs seem to mainly be used by smaller projects, or larger projects that are maintained by a few people.
I've also noticed that a lot of the time, the Changelogs used by other projects, are nothing more than CVS commit messages, in which case, we have that here ;)
Usualy a more accessable global Changelog is assembled in time for the actual release.
BTW, I'm not a KDE developer, so I'm only making guesses from what I've seen over the years
Becuase IMHO changelogs doesn't make sense if you have a cvs system.
In a cvs system, you put all your changes into the cvs commit comment, which is the best you can do. Later you will be able to use annotate and can see for each line of code, what was the reason for this line.
So using a comment in a commit is rather mandatory, if you want to use full cvs functionality.
Then, when you then want a changelog, just have a look into the comments.
Why should you then still maintain such a IMHO mostly useless changelog file?
Are you still interested one year later what was changing months ago whithout any relationship to the code? I doubt this strongly.
What we still maintain is a CHANGES file, which contains changes which is interesting for the user and not for the maintainer. This CHANGES file is then used for the remarks on the release.
Noatun and ksim crash when change preferences, is normal ? For example:
Change the skin type from kjofol to kaiman crash ... to minimal crash .. in the ksim quit
the uptime crash, change some skins crash, most people use gkrellm and xmms ...
Whats up with this apps ? or use gkrellm and xmms and no more problems ?
They both work pretty good for me (installed from source code)
Did you use the right RPM packages, are they known to work, have you looked in bugs.kde.org to see if somebody else reported a similar problem, have you filed a bug report, can you provide a backtrace...
This would be more helpful to the developers.
Comments
It can't be said enough: thanks a lot Derek !!!!!!!!!!!!!!!!!!!
I noticed that Derek uses a nice newer KDE 3.1-esque favicon for his site.. I think that www.kde.org and dot.kde.org perhaps should adopt it 8)
Yeah, it's nice...
>Yeah, it's nice...
And ceremoniously swiped from the kde icons. Melchior Franz helped me set it up.
Derek (trying out cvs konqueror)
Personally I envisaged a Crystalised version of the "K" rather than a gear.... I note that dot.kde.org and the cvs-digest are using very slightly different gears at the moment.
I'm happy to change the kde.org favicon.ico to a gear though, but I can't quite decide if I like the dot one or cvs digest one more at the moment.
Yeah, the kde.org favicon.ico should probably remain a K... it's pretty good already though old style.
Is there a release schedule made for KDE 3.1.1 , 3.1.2, etc.? I'm wondering it merges from Safari will make it into those.
KDE 3.1.1 release schedule:
http://developer.kde.org/development-versions/kde-3.1-release-plan.html
>wondering if merges from Safari will make it into those.
Don't think so. The large safari merges from the last 3 weeks weren't backported.
We'll have to wait for 3.2.
Derek
You're looking for a changelog, rather than a release schedule.
See here for the 3.1 to 3.1.1 changelog:
http://www.kde.org/announcements/changelogs/changelog3_1to3_1_1.php
Figuring out where the other changelogs are is a simple exercise :)
YEAHHH
another cvs-digest. looking forward for it every day!
Out of curiosity, but why don't you use ChangeLogs as any other project ? So everyone could look on their own what's changed. Many ChangeLogs in the kde modules are outdated for years or some projects simply don't have any.
Probably because of the scope of the project...
Changelogs seem to mainly be used by smaller projects, or larger projects that are maintained by a few people.
I've also noticed that a lot of the time, the Changelogs used by other projects, are nothing more than CVS commit messages, in which case, we have that here ;)
Usualy a more accessable global Changelog is assembled in time for the actual release.
BTW, I'm not a KDE developer, so I'm only making guesses from what I've seen over the years
Becuase IMHO changelogs doesn't make sense if you have a cvs system.
In a cvs system, you put all your changes into the cvs commit comment, which is the best you can do. Later you will be able to use annotate and can see for each line of code, what was the reason for this line.
So using a comment in a commit is rather mandatory, if you want to use full cvs functionality.
Then, when you then want a changelog, just have a look into the comments.
Why should you then still maintain such a IMHO mostly useless changelog file?
Are you still interested one year later what was changing months ago whithout any relationship to the code? I doubt this strongly.
What we still maintain is a CHANGES file, which contains changes which is interesting for the user and not for the maintainer. This CHANGES file is then used for the remarks on the release.
Philipp
KSpread developer
Noatun and ksim crash when change preferences, is normal ? For example:
Change the skin type from kjofol to kaiman crash ... to minimal crash .. in the ksim quit
the uptime crash, change some skins crash, most people use gkrellm and xmms ...
Whats up with this apps ? or use gkrellm and xmms and no more problems ?
They both work pretty good for me (installed from source code)
Did you use the right RPM packages, are they known to work, have you looked in bugs.kde.org to see if somebody else reported a similar problem, have you filed a bug report, can you provide a backtrace...
This would be more helpful to the developers.
Entire KDE desktop locks up for me with KDE 3.1 forcing reset button reboot.
Don't you have to love those very verbose wanna-be bug reports? :-)
I can't get my e-mail. Please help. (joke alert :)
Are you using a GeoForce?
If so, you shouldn't be having any problems if you use the 3190 drivers. Linux/X is rock solid with both a Athlon/GeForce2 and a Pentium4/GeForce4.