On Feb 26, 2010, at 9:55 PM, Michael Roberts wrote:
my experience is similar to Yanni, in that I found a series of updates, every so often, would break the build. it became a pain to keep on checking and fixing things. So i am spending my time on trying to script some sanity checks and logic for common errors. Given the pace of updates, whilst human intervention is the simple solution, i don't think it is great. One gets behind very quickly.
Also, how many developers regularly look at the test result pages (the first version on the wiki, the gforge /experimental, yanni's hudson setup) for the core image and act on the implied bugs in the update? i.e comment on the issue tracker related to the specific update just published
I think we need to email the delta of each test run to this mailing list as soon as it is run.
Yes I think that we should streamlined our process - fast running tests - faster tests -> we should have a look at the changes adrian kuhn sent - run and fix more often. Stef
thanks, Mike
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project