Linked by David Adams on Wed 10th Sep 2008 15:43 UTC, submitted by Michael Larabel
Thread beginning with comment 330071
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2006-02-15
This is where I step in to give my opinion, no matter if anyone is interested in hearing it or not.
X releases have been problematic forever and someone has to get it straightened out. Projects like GNOME don't seem to have these kinds of problems. GNOME generally has a roadmap that they follow very closely. If something isn't finished in time they postpone the release, but it is never for very long because they haven't promised more than they can deliver.
Indeed. Both GNOME and KDE are HUGE projects consisting of dozens of different packages but both projects are always on schedule and both seem to only promise what they know they can accomplish. But they have a different mindset from the beginning: promise what you know that can be kept, and don't start working on new features before the old ones are implemented. X developers seemingly rather start working on new features, discarding the promised ones, and delivering neither.
I am not saying they don't do good job. I couldn't do even nearly as good. But they need a roadmap and they need to stick to it. Jumping all over the place creates mess like this we've just got in our hands...