Linked by Thom Holwerda on Wed 22nd Jul 2009 12:29 UTC, submitted by lemur2
KDE The KDE project has announced that it has reached its one millionth commit to its Subversion repository, indicating that the KDE project is very healthy indeed. "This is a wonderful milestone for KDE," said Cornelius Schumacher, President of the KDE e.V. Board of Directors, "It is the result of years of hard work by a large, diverse, and talented team that has come together from all over the globe to develop one of the largest and most comprehensive software products in the world."
Order by: Score:
Congrats!
by kragil on Wed 22nd Jul 2009 13:30 UTC
kragil
Member since:
2006-01-04

The important bit is this:
"The 500,000th commit took place on January 19th, 2006, and the 750,000th commit 23 months later on December 18th, 2007. In contrast, only nineteen more months were required to reach the 1,000,000 commit milestone."

Now that they migrate to gitorious it will be much harder to track commits.

Well done, KDE!

Reply Score: 3

RE: Congrats!
by JohnFlux on Wed 22nd Jul 2009 13:57 UTC in reply to "Congrats!"
JohnFlux Member since:
2007-01-04

Harder with git? You have to be joking.

You can do:

git shortlog -s -n

Which shows the number of commits made by each person. You can get all sorts of statistics out easily.

Reply Score: 2

RE[2]: Congrats!
by kragil on Wed 22nd Jul 2009 14:11 UTC in reply to "RE: Congrats!"
kragil Member since:
2006-01-04

True for one git tree. But how do you integrate all the private git trees?

It is distributed, you know. So the true extend of work done might or might not be visible.

Reply Score: 2

RE[3]: Congrats!
by siride on Wed 22nd Jul 2009 14:29 UTC in reply to "RE[2]: Congrats!"
siride Member since:
2006-01-02

Anything that goes into KDE itself will end up in some primary repo somewhere, or into SVN if they are still using that as the main repo. The commits can get counted then. Commits in private repos are as irrelevant in Git as uncommitted working copy changes are in SVN.

Reply Score: 2

RE: Congrats!
by siride on Wed 22nd Jul 2009 14:11 UTC in reply to "Congrats!"
siride Member since:
2006-01-02

Uhh, will it? All the commits that make it into the mainstream will be in one repo somewhere and those can easily be counted:

git log --pretty=oneline | wc -l

Except that it's also really easy to count arbitrary ranges of commits, such as how many commits were made between tags, which is much more difficult in SVN (probably requires manual involvement, unless properties are used to indicate where a tag or branch was made).

Reply Score: 3

RE: Congrats!
by fithisux on Thu 23rd Jul 2009 07:19 UTC in reply to "Congrats!"
fithisux Member since:
2006-01-22

Congrats.

I love their products.

Reply Score: 2

ParanoidAndroid
Member since:
2006-03-26

Sounds impressive but I would like to see more bugs fixed instead of "the next big plasma applet". The number of open bugs is probably the same as the number of commits and it's a shame some bugs have been open for years (even when people vote for them).

Reply Score: 5

Isolationist Member since:
2006-05-28

I completely agree with this, but it is a shame some KDE fan boy has modded you down ..

Reply Score: 0

siride Member since:
2006-01-02

He was modded down for being incorrect. The KDE devs do spend a lot of time fixing bugs, but KDE is a big project and so will have a lot of bugs. That's just the way it is. Also, old bugs aren't going to be fixed because they apply to KDE 3.5 and that is no longer being developed or supported (despite some distros still using it).

Here is what Bugzilla shows for the last 7 days: https://bugs.kde.org/weekly-bug-summary.cgi

Notice how half of the projects/components have actually closed more bugs than were open at the start of the week?

And for the last 31:
https://bugs.kde.org/weekly-bug-summary.cgi?tops=20&days=31

It's a little bit worse, but not by much. Plasma, while having a net increase of 68 bugs, still closed well over 600 bugs in one month. That's a pretty big deal.

So to say that they aren't fixing bugs is just nonsense.

Reply Score: 20

ParanoidAndroid Member since:
2006-03-26

I didn't say no bugs were getting fixed. But, for example keyboard shortcuts don't work properly since 4.0.0. They were scheduled to be fixed in 4.1, then 4.2, 4.3 etc. and they still don't work as of now. At the same time many new plasma stuff is added while the bugs pile up. So maybe it's time to stabilise at one point in time first.

Reply Score: 1

siride Member since:
2006-01-02

So your pet bug isn't be fixed. Cry me a river. You also assume that the people adding plasma features are the same ones who might otherwise be fixing your pet bug.

Perhaps you should contact the developer assigned to your bug directly and bug them about it?

Reply Score: 7

ParanoidAndroid Member since:
2006-03-26

It's just one example of a long list. Make a list of the most voted bugs and see how many are still open after long periods of time.

Reply Score: 3

boudewijn Member since:
2006-03-05

Well, first of all your flippant "the number of bugs will be similar to the number of commits" is, of course, nothing but unhelpful hyperbole. There are about 22000 bugs in a project that encompasses hundreds of libraries and applications and at the last count, excluding extragear, about 5 million lines of code. Note that bugs and commits include extragear. This is actually a pretty impressive ratio.

Second, you attitude shows you don't know how a free software project operates. Your mind works in the corporate developers-are-exchangeable-resources model. That's completely inappropriate. It's even inappropriate for a corporate setting, but it doesn't apply at all here.

Nobody within KDE can reassign anyone to something. Nobody within KDE even wants to tell someone who shows up with his first plasma widget "don't commit it, first fix Paranoid Android's bug". We're way too happy having gained a new contributor.

And then, yes sometimes people leave bugs to fester for way too long. I'm guilty of that. I don't like it. There are Krita bugs that I have wanted to fix three years ago, and they are really nasty. But I'm not going to let Paranoid Android dictate my priorities. I reserve the right to fix an underlying problem first before tackling Paranoid Android's problem, a guy I don't even know and who engages in meaningless hyperbole and who very likely hasn't even participated in a small free software project, let alone one as big as KDE.

(And, for the record: I am still the fasters KDE bugfixer over the past year, with 2 minutes from bug to fix! So there!)

Reply Score: 11

Slambert666 Member since:
2008-10-30

There are about 22000 bugs in .... KDE..


It sure feels that way!

Reply Score: 0

leos Member since:
2005-09-21

I didn't say no bugs were getting fixed. But, for example keyboard shortcuts don't work properly since 4.0.0.


Bug #? Works just fine for me. I remember some problems in earlier releases, but its been fine since 4.2 for me.

Reply Score: 7

Congratulations!
by drstorm on Wed 22nd Jul 2009 14:03 UTC
drstorm
Member since:
2009-04-24

Great job, KDE team. ;)

In my opinion(!), KDE is by far the best desktop on *nix, and I'd like to see it going for many years to come.

Best wishes and congratulations!

Reply Score: 4

Moving to git...
by droidix on Wed 22nd Jul 2009 14:06 UTC
droidix
Member since:
2008-03-13

Which parts of KDE are moving over to Git?

Reply Score: 1

RE: Moving to git...
by TheMonoTone on Wed 22nd Jul 2009 15:42 UTC in reply to "Moving to git..."
TheMonoTone Member since:
2006-01-01

All of it at some point.

Reply Score: 3

RE: Moving to git...
by andy_js on Wed 22nd Jul 2009 15:45 UTC in reply to "Moving to git..."
andy_js Member since:
2008-02-29

The bits that GNOME wrote.

/jk

Reply Score: 1

RE: Moving to git...
by mgl.branco on Wed 22nd Jul 2009 15:47 UTC in reply to "Moving to git..."
mgl.branco Member since:
2009-07-22

Only Amarok has already moved to git but the whole KDE project will eventually do the same. What I understand is that the when and how hasn't been decided yet. KDE is going to wait how things work up with Amarok and only then migrate.

Reply Score: 3

RE[2]: Moving to git...
by droidix on Wed 22nd Jul 2009 15:54 UTC in reply to "RE: Moving to git..."
droidix Member since:
2008-03-13

Ok, that makes sense, thanks for the info!

Reply Score: 1

RE[2]: Moving to git...
by smitty on Wed 22nd Jul 2009 18:34 UTC in reply to "RE: Moving to git..."
smitty Member since:
2005-10-13

I think there was some chatter about doing it in September, but obviously it's going to depend on how well things go with Amarok's test run.

They definitely wanted to try to transition everything over during the 4.4 development window, and they don't want to do it too late in the cycle to keep from interfering with the beta releases and bugfixing.

Reply Score: 3

v wow
by loganmoore on Wed 22nd Jul 2009 17:42 UTC
v You know ...
by Isolationist on Wed 22nd Jul 2009 18:18 UTC
RE: You know ...
by Isolationist on Thu 23rd Jul 2009 19:19 UTC in reply to "You know ..."
Isolationist Member since:
2006-05-28

Geeks!

Reply Score: 1

KDE 4.3 RC3 Release Announcement
by lemur2 on Thu 23rd Jul 2009 00:13 UTC
lemur2
Member since:
2007-02-17

Although KDE 4.3 release is due out in just a couple of weeks time, KDE.org have announced a third release candidate version.

http://kde.org/announcements/announce-4.3-rc3.php

KDE Community Ships Third Release Candidate of KDE 4.3 Free Desktop, Containing Many New Features and Improvements

July 22nd, 2009. The KDE Community today announced the immediate availability of KDE 4.3 RC3, a release candidate of the 3rd iteration over the KDE 4 desktop, applications and development platform.

While 4.3 already feels very stable, there still have been quite some changes to the code-base since the second release candidate. In order to have the 4.3.0 release well-tested, the release team decided to put out another release candidate and postpone the final 4.3.0 release by one week. The most notable change is probably a fix for a performance problem in Plasma, where applets would shortly freeze after being resized. This bug has been resolved by delaying the caching of rendered SVG images until after the resizing has finished.


Performance improvements are always welcome.

Edited 2009-07-23 00:15 UTC

Reply Score: 4

v KDE 7
by Jason Bourne on Thu 23rd Jul 2009 15:30 UTC
Just finish it already...
by ruel24 on Thu 23rd Jul 2009 21:23 UTC
ruel24
Member since:
2006-03-21

I'm happy for KDE, but it's still incomplete as of 4.2.4, and it's still buggy. KDE 4.3 may or may not iron out some of this, but we're deep into a release and it's still incomplete and buggy. I agree with an earlier poster that I'd rather see quality instead of the next big Plasma release, or whatever. Give me substance over flash.

I really find it funny that despite running a Core i7 920 and an nVidia 275GTX card with 6GB of memory, my KDE 4.2.4 installation gives me a notification now and then that compositing was too slow and it's temporarily turning it off. What? So, is the resources for KDE gotten to the point that Vista requires, now?

Reply Score: 2

RE: Just finish it already...
by sebas on Sat 25th Jul 2009 11:19 UTC in reply to "Just finish it already..."
sebas Member since:
2008-02-02

Not quite, what you see is that code kicked in that prevented your desktop from becoming unusable due to bad video drivers (too little frames being rendered for compositing to be useful).

The nvidia driver still has grave performance problems, even my integrated intel chip feels faster than my desktop's 7600GS. I know it's frustrating for users, but we (KDE) decided to not paper over driver bugs so they eventually get fixed and don't stand in the way anymore in the future.

Reply Score: 1