On Sep 16, 2010, at 9:55 AM, Simon Denier wrote: try but we will break Moose. So may be investing one week would solve that problem is better than getting in 1.2.

We want both, but for completely different reasons: 1) 'Namespace' (and robust) importer to load any pharo code into a working Moose image. But could we run the tests and the lint rules in such a namespace? It's also important to build a report. 2) Load moose into pharo 1.2 just because early migration is less painful than late migration where you have to change a lot. So as soon as Pharo 1.2 is stable enough, we can move the Moose #bleedingEdge (to use the forthcoming Metacello terminology) to Pharo 1.2 Cyrille already worked in this direction and Moose did not break so much if I remember (at least at load time). On 16 sept. 2010, at 12:07, Laval Jannik wrote: That could be an interesting idea. We have to take care that the importer works well in Squeak in this case. -- Simon