Do more extenstive testing before designating a revision of Ptolemy as stable
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."
#3 Updated by Chad Berkley over 11 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.