<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap:break-word;line-break:after-white-space"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">On June 6, 2018 at 4:21:35 AM, Boespflug, Mathieu (<a href="mailto:m@tweag.io">m@tweag.io</a>) wrote:</div> <div><blockquote type="cite" class="clean_bq" style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span><div><div></div><div>I understand that some people out there are concerned about the GitHub<span class="Apple-converted-space"> </span><br>acquisition. But at this point in the maturity of the infrastructure,<span class="Apple-converted-space"> </span><br>there are more pressing concerns than what will Microsoft do.<span class="Apple-converted-space"> </span><br><br>* As seen here, <a href="https://circleci.com/gh/ghc/ghc">https://circleci.com/gh/ghc/ghc</a>, master is currently<span class="Apple-converted-space"> </span><br>red on everything but x86_64-linux (sans LLVM, sans Hadrian).<span class="Apple-converted-space"> </span><br>* This means that starting from a stock Debian Jessie, we can't get<span class="Apple-converted-space"> </span><br>validate to pass on stock virtualized infrastrure (except for one).<span class="Apple-converted-space"> </span><br>* So the first order of business is to get ghc HEAD to a sufficient<span class="Apple-converted-space"> </span><br>level of quality that validate passes everywhere and so that CI<span class="Apple-converted-space"> </span><br>becomes useful.<span class="Apple-converted-space"> </span><br>* None of this work is GitHub specific. Nor all that CircleCI or<span class="Apple-converted-space"> </span><br>Appveyor specific for that matter (work is currently focused on<span class="Apple-converted-space"> </span><br>improving the test suite).<span class="Apple-converted-space"> </span></div></div></span></blockquote></div><p>Right. This all sounds like good work, and a good priority to focus on, and doesn’t seem to involve needing to make any short-term decisions about changing the patch and review workflow. So it sounds like we have our hands full already and should just let things settle for the time being, and proceed as Ben has suggested :-)</p><p>Cheers,</p><p>Gershom</p></body></html>