[kepler-dev] [Bug 4091] - Make it so the build system can use a "blessed" version of Ptolemy.

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4091


welker4kepler at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Comment #2 from welker4kepler at gmail.com  2009-05-26 10:46 -------
I agree with you that the word "stable" is better than "blessed" and that is
the the word used in one of several new build system commands. The basic
infrastructure for this task is not complete. However, right now, the only
testing that is done is to ensure that Kepler still compiles against the head
of Ptolemy (which also must compile). If that happens, then the revision
associated with the head of Ptolemy is considered to be "stable" and is
designated as such so that any command that invokes "ant update" "ant get" or
"ant change-to" directly or indirectly will now retrieve the new stable version
of Ptolemy.

Clearly, some errors will still get through, so testing that goes beyond
compilation would be desirable. For example, if configuration files in Ptolemy
were to be moved and the references to those files in Kepler not updated, this
would cause run time incompatibilities that would not be caught under the
current approach. However, the point of this exercise is not to give Kepler
trunk developers 100% stability (if developers want such stability, the should
work off a published version of Kepler) but instead to greatly increase
stability. Furthermore, since the "stable" revision is stored in PTII, any
update to an older version of Kepler will get the corresponding version of
Ptolemy. So, it is very easy to step back to working with a slightly older
revision of Kepler (and Ptolemy) with a single command of the form: "ant update
-Drev={$revision}."

Nonetheless, more testing would be desirable. And we now have the
infrastructure that makes it very easy to add such tests when we get around to
deciding exactly the nature of whatever additional tests we want. However, for
now, I am going to move on to work on other tasks. This bug is therefore
closed. However, I am opening a new bug that references the desirability of
doing more extensive testing of Ptolemy.