On 29 January 2013 14:57, Marcus Denker <[email protected]> wrote: > > On Jan 29, 2013, at 2:49 PM, Camillo Bruni <[email protected]> wrote: > >> if you guys would 10 seconds to read the jenkins configuration you would see >> that >> we use the COG vm >> >> wget --quiet -qO - http://pharo.gforge.inria.fr/ci/script/ciPharo20CogVM.sh >> | bash >> >> and most of the builds on https://ci.inria.fr/rmod use the NBCogVM >> >> wget --quiet -qO - >> http://pharo.gforge.inria.fr/ci/script/ciPharo20NBCogVM.sh | bash >> >> >> !!!!PLEASE BOOKMARK!!!! >> >> all vms are archived on the gforge, >> >> DO NOT USE JENKINS TO DOWNLOAD VMS... >> >> http://pharo.gforge.inria.fr/ci/vm/ >> >> they are all sorted by type and platform. Currently the PharoVM us not so >> stable. >> => stack, cog or nbcog are better choices >> > > The goal of course is to have *one* VM… else this is very very complex. >
But it is impossible to have just one. Because it is against development process, same as with images: we have 2.0 beta, 1.4 stable [+seaside preloaded] [+ project Foo preloaded ] (not speaking about older versions).. Why you think what is normal for image-side, should be banned for VM side? And while i agree that we should minimize the confusion, i do not see how we can avoid having zoo of VMs around. > Marcus -- Best regards, Igor Stasenko.
