Re: Good Call

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: Good Call
by Debian User on Sunday 02/Dec/2007, @04:53

You know what a release candidate is good for as well? Testing if it is a release candidate!

Only now it's obvious that deadlines were missed and a schedule extension is necessary. Notice how the delay announcement is shortly after the release candidate has been found incomplete.

But you will never know, if you are not making deadlines, what people have sitting in their checkouts, and another Beta wouldn't be a hard enough deadline, or else things would already be there.

Yours,
Kay

Related Links

·   Articles on KDE Official News
·   Also by Debian User
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Good Call
by Jim on Sunday 02/Dec/2007, @07:09

> Only now it's obvious that deadlines were missed and a schedule extension is necessary. Notice how the delay announcement is shortly after the release candidate has been found incomplete.

No, I think it was plainly obvious beforehand. Look at the list of current showstoppers. Plasma:

> goal: A basic panel is there; current work is to flesh it out into a more capable panel system. System tray and taskbar both need work as does a desktop containment with legacy support for the Desktop folder.

This is clearly not ready for release, you don't need millions of testers to realise that. It is not the surprise that you are making it out to be.

> But you will never know, if you are not making deadlines, what people have sitting in their checkouts, and another Beta wouldn't be a hard enough deadline, or else things would already be there.

Nobody is arguing against deadlines, only against unreasonable ones that don't reflect the state of the code. And the idea that a release candidate is meant to prompt people to commit code is ludicrous.

[ Reply To This | View ]

Re: Good Call
by eMPee584 on Monday 03/Dec/2007, @02:29

> And the idea that a release candidate is meant to prompt people to commit code is ludicrous.
Well, so is reality. Actually It is quite clear that the code would have been far less ready if the original schedule stated the January release date in the first place. Honestly, who cares about the integrity of the term 'release candidate' and its correct usage. Whatever - let's rather finish this thing. Then we can call it 4.0-stable.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"We've been wondering, are Andreas Pour and Navindra Umanee the same person?" -- Charles Samuels
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.