Bug #4108

Do more extenstive testing before designating a revision of Ptolemy as stable

Added by David Welker over 13 years ago. Updated over 12 years ago.

In Progress
build system
Target version:
Start date:
Due date:
% Done:


Estimated time:


Right now, before a revision of Ptolemy is considered "stable" all it must do is be able to compile and the trunk of Kepler must be able to compile against it. However, this will not catch run time problems caused by changes in Ptolemy. It would therefore be desirable to perform more extensive tests in order to catch at least some of the possible run-time problems that might be caused by changes in Ptolemy before dedsignating the new revision of Ptolemy as "stable."


#1 Updated by David Welker over 13 years ago

I am not sure that more extensive testing is really necessary. There have been very few developer problems associated with Ptolemy since we have implemented a compile test before interacting with the trunk of Ptolemy.

#2 Updated by David Welker over 12 years ago

Additional testing before designating a version of Ptolemy as "stable" is unnecessary. Closing this bug.

#3 Updated by Chad Berkley over 12 years ago

I don't think this bug should be closed. I'm changing it to be a lower priority but reopening it. I think that there should be more testing done on the "stable" ptolemy build if we're going to have that functionality. As we get more test for Kepler in general, better testing can be added to this task.

#4 Updated by Redmine Admin over 9 years ago

Original Bugzilla ID was 4108

Also available in: Atom PDF