<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
> <span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">I don’t see too much utility in saving literally hundreds of builds given they we can use git bisect to hunt for regressions. That should keep the storage requirements in check, right?</span><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Hmm... we need some mechanism to pin a version that we want to test as a release candidate.</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Best,</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Marcel</span></div><div class="mb_sig"></div><blockquote class='history_container' type='cite' style='border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;'>
<p style='color: #AAAAAA; margin-top: 10px;'>Am 04.02.2021 17:54:19 schrieb Eliot Miranda <eliot.miranda@gmail.com>:</p><div style='font-family:Arial,Helvetica,sans-serif'> <br><br><br>> On Feb 3, 2021, at 2:42 PM, Levente Uzonyi <leves@caesar.elte.hu> wrote:<br>> <br>> Why not use files.squeak.org?<br><br>Also +1.<br><br>I’d love to see two builds, the latest known good build that has passed all tests, and the latest build that compiled but might be broken.<br><br>I don’t see too much utility in saving literally hundreds of builds given they we can use git bisect to hunt for regressions. That should keep the storage requirements in check, right?<br><br>We do of course still need to retain release VMs.<br>> <br>> <br>> Levente<br>> <br></leves@caesar.elte.hu></div></blockquote>
</div></body>