Hi. I found a bug in Pharo, and I started wondering how to determine where it came from. I checked a few methods in the debugger to see if they had recently been modified, but that was no help. I checked the change sorter to see if it had any idea what had been recently installed, but it was choked by Monticello updates. Then I opened a new Pharo Image in order to try each update one by one (whatever Monticello you guys use to load your changes is *really* slow. I gotta fix you guys up with MC1.6). But before I did that, I noticed on the right of the screen is something that looks like a change log. And at the bottom, it said: (full list of changes: print "ScriptLoader new logContents") So I tried it in my 10091 image, and sure enough, it printed up a changelog. So I went to see what this mysterious class ScriptLoader is. I found a whole lot of methods. Some looked auto-generated. Some seemed to be convenience methods for loading MC packages from Pharo and PharoInbox. It looks kind of like Installer, which I am more familiar with. I'm rather curious now about how you manage Pharo. I took a look at http://code.google.com/p/pharo/wiki/HowToContribute and wondered what happens after that. I now imagine it involves ScriptBuilder building the update, and then something uploading it. What is the mechanism? How is Pharo tested? is it regularly tested by someone using TestRunner, or something fancier? What are all the auto-generated methods in ScriptLoader for? How do you typically trace a bug from image to problem package to update to issue? I'm interested because keith and I are building a build server that is able to build images, build packages, load packages, run tests, build VM's and such, all automated and with an easy interface. So far, we have the easy interface (Installer), but are still working on making it do more. So I'm interested in learning how it works here, so that we can at least end up with something as good as this -- Matthew Fulmer -- http://mtfulmer.wordpress.com/