[Box-Admins] Re: SqueakTrunk build vanished?!

[Frank Shearar]

I appreciate that we don't want to get left behind, but I also don't
see the need to keep right on the bleeding edge. I'm happy for us to
try out the latest build - it looks like they might have fixed the
Ruby issue - and if necessary revert.

When would be a convenient time for such an experiment?

frank

On 6 July 2013 21:08, Ken Causey <ken at kencausey.com> wrote:
> We are now 5 releases behind on Jenkins (1.517 -> 1.522).  What can be done
> to allow us to track releases again while having all builds continue to
> work?
>
> Ken