but we need an inbox for configurations and a method to move thrusted configs to metarepo, otherwise, we will have same mess we have in MetacelloRepository really soon.
On Jun 20, 2012, at 10:27 AM, Stéphane Ducasse wrote: > esteban > we should let people publish early and fix by hand and in parallel we work on > it. > I will try to get a stab at a sketch today > > stef > On Jun 20, 2012, at 10:17 AM, Esteban Lorenzano wrote: > >> Problem is who validates the packages? (we are working in some >> automatization here, but it will take time) >> For example: ConfigurationOfSeaside30 in MetaRepoForPharo14 does not loads >> well (since it loads a stripped version of OB, if you have Nautilus it fails >> and if not it breaks Shout). >> It is easy to fix, but nobody seems to want... >> >> Esteban >> >> On Jun 20, 2012, at 10:13 AM, Sven Van Caekenberghe wrote: >> >>> >>> On 20 Jun 2012, at 10:01, Stéphane Ducasse wrote: >>> >>>>> and wonder why we dont use a >>>>> http://ss3.gemstone.com/ss/MetaRepoForPharo20. >>>> >>>> We can use it too for now. >>>> What is missing is the process behind >>> >>> Let's use that then: it is important that during 2.0 development, you can >>> easily load (validated) metacello configs; many of us are using 2.0 daily, >>> as in eating our own dogfood, if metacello configs + browser are the way >>> forward, we should start using that now. >>> >>> Sven >> >> > >
