<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br><div style="font-family: Helvetica; font-size: medium; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); -webkit-text-size-adjust: auto; "><br></div><div style="font-family: Helvetica; font-size: medium; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); -webkit-text-size-adjust: auto; ">--<br>sent via mobile</div></div><div><br>On 17 Sep 2013, at 03:01, Francois Berenger <<a href="mailto:berenger@riken.jp">berenger@riken.jp</a>> wrote:<br><br></div><blockquote type="cite"><div><span>On 09/17/2013 03:14 AM, Anil Madhavapeddy wrote:</span><br><blockquote type="cite"><span>On 13 Sep 2013, at 07:47, Francois Berenger <<a href="mailto:berenger@riken.jp">berenger@riken.jp</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>For example, are all the packages in OPAM</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>checked regularly to compile on various architectures?</span><br></blockquote></blockquote><span></span><br><span>As I have some packages in OPAM (vector3, dolog),</span><br><span>I would like to receive an automatic e-mail if one of my packages is broken on some arch.</span><br></div></blockquote><div><br></div><div>Since we're using GitHub in the workflow and plan to update the pull request thread with OCamlot comments, anyone involved in (or watching) the PR thread would automatically receive updates via GitHub. We need stable links for this to work properly. </div><div><br></div><div>You can get an idea of the workflow via the screen cast I made earlier this year:</div><div><a href="http://vimeo.com/m/61768273">http://vimeo.com/61768273</a></div><div><br></div><div><br></div><br><blockquote type="cite"><div><span></span><blockquote type="cite"><span>There is; see my recent write up on its status here:</span><br></blockquote><blockquote type="cite"><span><a href="http://anil.recoil.org/2013/09/09/ocamlot-autotriaging.html">http://anil.recoil.org/2013/09/09/ocamlot-autotriaging.html</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>We're working on making the results more easily accessible via</span><br></blockquote><blockquote type="cite"><span>permalinking and archiving, but for now the results are triaged</span><br></blockquote><blockquote type="cite"><span>by me in OPAM bugs such as:</span><br></blockquote><blockquote type="cite"><span><a href="https://github.com/OCamlPro/opam-repository/issues/1029">https://github.com/OCamlPro/opam-repository/issues/1029</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Fixes to any of those most welcome!</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>-anil</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><span></span><br><span>_______________________________________________</span><br><span>Infrastructure mailing list</span><br><span><a href="mailto:Infrastructure@lists.ocaml.org">Infrastructure@lists.ocaml.org</a></span><br><span><a href="http://lists.ocaml.org/listinfo/infrastructure">http://lists.ocaml.org/listinfo/infrastructure</a></span><br></div></blockquote></body></html>