<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div style="font-size: 18px; ">I contend that for the latter, it does not matter how the fixed-point image was created, just that you continuously build and test your application against frequent releases, and work with the community to quickly fix any compatibility issues that arise. Isn't this true?</div></div><div style="font-size: 18px; "><br></div><div style="font-size: 18px; ">Thanks,</div><div style="font-size: 18px; ">Josh</div></div></blockquote><br style="font-size: 18px; "></div><div style="font-size: 18px; ">It would be lovely, but it just doesn't happen. Ask etoys, cobalt, sophie, gjallar. They all started large projects and did not find the time or the effort to track subsequent squeak releases. One problem is that individual releases were too revolutionary for many, trying to to do much in one go, this can be helped by release early and often. More than that the release teams didn't take any responsibility for the migration path. (e.g. Smalltalk -> SmalltalkImage)</div><div style="font-size: 18px; "><br></div><div style="font-size: 18px; ">This same problem occurs at a package level too. I am stuck about 150 (or more now) revisions behind in Pier, because my modifications to pier (which I do keep in a separate package), are effectively (but accidentally) a fork. In trying to solve the problem, the more I see the tools, i.e. Monticello as part of the problem. However at present the solution alludes me.</div><div style="font-size: 18px; "><br></div><div style="font-size: 18px; ">K.</div></body></html>