On Aug 9, 2011, at 7:28 AM, Lukas Renggli wrote:
> Ahh ok, I will rebuild my images then. I was using the ../unstable-core URL.
>
Yes, this points to gforge and laggs the very latest by around 10 updates. The
image
is always one that we know is not completely broken. (because very last update
could
be not in a good state).
The other reason is that Hudson needs to start somewhere... and loading update
is
slow and tends to stress squeaksource. So Hudson takes the gforge image as a
starter.
Of course all that is done by hand (me uploading, me changing links... or even
having
to tell Adrian to change links).
This is all not perfect, but there is always the question: Do we stop to
improve Pharo
until the process is perfect or do we do both in parallel?
This can and will all be improved, step by step.
Marcus
--
Marcus Denker -- http://marcusdenker.de
