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

Well, at the very least, we are learning a lot from this release J.

 

Great points all, and thanks for bringing this up John.

 

Cheers,

Doug Schaefer, QNX Software Systems

Eclipse CDT Project Lead, Tools PMC member

http://cdtdoug.blogspot.com

 


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

 


Yes, I have been entering bugs for the issues I have seen.  Perhaps the issue here is more about managing expectations.  The announcement on the main eclipse.org page says "Eclipse Callisto RC1 is available".  I think the broader community seeing this announcement may get the mistaken impression (as I did) that this is in fact a release candidate.  If they take the time to download it and very basic tire kicking doesn't work or creates many errors, it may turn people off from trying it further.  I didn't mean to light any fires, I'm sure there is still plenty of time to get things in shape for the release.

John


Doug Schaefer <DSchaefer@xxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

27/04/2006 03:03 PM

Please respond to
Cross project issues

To

Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

cc

 

Subject

RE: [cross-project-issues-dev] Callisto quality

 

 

 




I think it is important, especially for members of the Platform team, to realize that not everyone is at an RC status in Callisto. We’re still trying to adapt to the last minute changes that have gone into the platform, and that was the purpose for the Platform to go RC a month earlier than it has in the past.
 
If there are things not working, please make sure you communicate them to the appropriate project teams. There is still time to address them and make content changes if necessary.
 
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, Tools PMC member
http://cdtdoug.blogspot.com
 

 



From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault
Sent:
Thursday, April 27, 2006 2:47 PM
To:
Cross project issues
Cc:
Cross project issues; cross-project-issues-dev-bounces@xxxxxxxxxxx
Subject:
RE: [cross-project-issues-dev] Callisto quality

 

I agree.

Olivier Thomann/Ottawa/IBM@IBMCA
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

04/27/2006 02:40 PM

 

Please respond to
Cross project issues

 

To

Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

cc

 

Subject

RE: [cross-project-issues-dev] Callisto quality


 

 

 

 





John,

Your point is important especially if Callisto is publicly announced.
People might see it as an example of what quality the Eclipse foundation
can deliver. So we need to provide a Callisto release that looks really
good and rock solid. I did some testing and I have to admit that I have
been disappointed. I didn't expect basic scenarios to fail in a RC1
release.

Olivier




Doug Schaefer <DSchaefer@xxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
2006-04-27 14:31
Please respond to
Cross project issues


To
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc

Subject
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
http://cdtdoug.blogspot.com


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?

John_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Back to the top