On Jan 11, 2010, at 2:28 PM, Mariano Martinez Peck wrote: > > > On Mon, Jan 11, 2010 at 2:24 PM, Stéphane Ducasse <[email protected]> > wrote: > > > > Mariano > > > > I think that projects should publish in their repository a > > ConfigurationOfXXX > > and when this is stable copy it to MetacelloRepository. > > > > I agree more or less. Depends what you are meaning with stable. It is ok to > > commit ConfigurationOfXXX in your own repository until you have a first > > version. I just did that with SqueakDBX, but for the rest of the projects, > > I commit to local repo until it worked. And then, directly to > > MetacelloRepository. Of course, each person can do whatever they want. > > > > Then, you can directly commit it to MetacelloRepository. However, after > > that, the ConfigurationOfXXX can perfectly be unstable, using another > > version. For example, if you take ConfigurationOfPharo and load the version > > 1.0, it will work. Howver, it won't with 1.1 because I am still working. > > my point is that we should pay attention and have a limited set of > configuration that are working for each release. > I imagine > > ConfigurationOfMoose4-Pharo1.0 > ConfigurationOfMoose4.1-Pharo1.0 > ConfigurationOfMoose4.1-Pharo1.0-105005 > ConfigurationOfMoose4.1-Pharo1.1 > > Not unstable version. Commit in the pharoTaskForces if this helps you. > > > Stef: On Friday we can see it together because that's not the idea of > Metacello. You will have only ONE class ConfigurationOfMoose which will have > different versions. Then you will be able to evaluate: > > (ConfigurationOfMoose project version: '4.1') load
ok > > or whatever... > > But anyway, it will be better to see it together. > > Cheers > > Mariano > > > > > > Ok. No problem for me. My own "advice" is to put it *also* in > > MetacelloRepository. > > But we should get some guidelines else soon this will be a mess. > I suggest that we get a list of working stable configuration all the other > should be moved into PharoTreated or something like that. > > Stef > _______________________________________________ > 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 _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
