Hi Mariano, 2010/5/16 Mariano Martinez Peck <[email protected]>
> Hi folks. We have been discussing a lot what to do with the Metacello > configurations of all projects and MetacelloRepository. > We want several things: > > - Have an specific catalog of the working and tested packages/projects for > each Pharo release (1.0, 1.1, etc). > - Be able to have a hudson server running and testing such configurations. > - Unified way to load a project. > > For such objectives, we propose the following scheme: > > 1) We create a squeaksource repository called Pharo10MetacelloRepository > 2) All the Metacello configurations that are known and tested to work > perfect in Pharo1.0, are copied to such repository. (this takes 2 minutes) > 3) Now, we have the problem of WHICH version from the conf class should be > the one that loads and works in Pharo 1.0. So, once you copied the > configuration, then you have to implement a class side method "load" that > loads the exact version that should work in Pharo1.0. This version may not > be the last. And you already may have defined "load" to load the last > version. In such case, you can just change it for the version in the > Pharo10MetacelloRepository. Otherwise, we can use another message. Give us > your opinion. > > So the idea is that all developers/maintainers of Metacello configurations, > do that and publish it. With this, if you want to know which projects work > on Pharo 1.0 you just browser Pharo10MetacelloRepository, load the > repository you want, and you know that just doing "ConfigurationOfXXX" load > will do the job. > > In addition to this, we are able to have a hudson server that every XX > time, it scans the repository, and for each project it tries to load it and > report if there is a problem. We can even make that "load" loads also the > tests and make Hudson to run the tests. Or if you want we can use another > message than load. > > So...this is just an idea. But we need feedback and hear opinions. Because > Pharo 1.1 will be soon and would be great to have this already working for > Pharo 1.0. > I think Andreas' recent post to squeak-dev<http://lists.squeakfoundation.org/pipermail/squeak-dev/2010-May/150658.html>is most cogent o this topic: > > Thanks > > Mariano > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
