Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cross-project-issues-dev] Callisto quality

I’m not clear what point you are trying to raise, but I do hope you’ve raised bugs for the issues you’ve seen.


Doug Schaefer, QNX Software Systems

Eclipse CDT Project Lead, Tools PMC member


From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of John Arthorne
Sent: Thursday, April 27, 2006 2:18 PM
To: cross-project-issues-dev@xxxxxxxxxxx
Subject: [cross-project-issues-dev] Callisto quality


Are there any quality goals set for the Callisto release?  I ask because I have been playing around with Callisto RC1, and it is nowhere near what I would expect in quality from a release candidate.  I don't want to call out any projects in particular, but some very basic scenarios I tried either didn't work at all or failed with various exceptions.  After a couple of hours of simple testing I had 10MB of errors in my log file.  There is time left to fix these bugs, but it seems worth asking the hypothetical question about quality criteria for the release.  In other words, is the goal to ship all ten projects on June 30th come hell or high water, or would either the set of projects or the date be changed if quality goals are not met?  Again, I don't want to induce acrimony or panic, but it seems fair to ask whether the function set, the quality, or the ship date are set in stone.  Often, one or more of these must slip in any successful release, but which would it be in the case of Callisto?


Back to the top