On Aug 9, 2011, at 7:58 AM, Lukas Renggli wrote: > Generally building an image should not stress SqueakSource much because all > packages are cached (at lest if you use a simple gofer script). For a > complete Seaside 3.0 build this is typically no more than a few requests > (listing + the packages that changed). > > So this means that I should search on gforge to get the latest working > version? > Ah, no.... the http://www.pharo-project.org/pharo-download/unstable-core actually points to the build server and should be up to date. (this is for the unstable, only stable points to gforge).
So for tracking the latest, http://www.pharo-project.org/pharo-download/unstable-core is good. (even for stable, as this does not change and so gforge is up to date). We need to release 1.3, I am getting confused about everything. Marcus -- Marcus Denker -- http://marcusdenker.de
