<div dir="ltr"><div>This is incredible! Now let's get them all compiling and running unit tests on Travis!<br><br></div>Yotam<br><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Mar 25, 2014 at 12:40 PM, Anil Madhavapeddy <span dir="ltr"><<a href="mailto:anil@recoil.org" target="_blank">anil@recoil.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">As a followup to this, I've written a script that syncs all the<br>
open pull requests against the compiler as OPAM compiler switches.<br>
This is now running live on the central OPAM respository.<br>
<br>
For instance, if you now `opam update` and look at your switches:<br>
<br>
$ opam switch --all<br>
-- -- 4.02.0dev+pr10 Add String.{split,rsplit}<br>
-- -- 4.02.0dev+pr13 Add String.{cut,rcut}.<br>
-- -- 4.02.0dev+pr14 Add absolute directory names to bytecode format for ocamldebug to use<br>
-- -- 4.02.0dev+pr15 replace String.blit by String.unsafe_blit<br>
-- -- 4.02.0dev+pr17 Cmm arithmetic optimisations<br>
-- -- 4.02.0dev+pr18 Patch for issue 5584<br>
-- -- 4.02.0dev+pr2 Parse -.x**2. (unary -.) as -.(x**2.). Fix PR#3414<br>
-- -- 4.02.0dev+pr20 OCamlbuild: Fix the check of ocamlfind<br>
-- -- 4.02.0dev+pr3 Extend record punning to allow destructuring.<br>
-- -- 4.02.0dev+pr4 Fix for PR#4832 (Filling bigarrays may block out runtime)<br>
-- -- 4.02.0dev+pr6 Warn user when a type variable in a type constraint has been instantiated.<br>
-- -- 4.02.0dev+pr7 Extend ocamllex with actions before refilling<br>
-- -- 4.02.0dev+pr8 Adds a .gitignore to ignore all generated files during `make world.opt'<br>
-- -- 4.02.0dev+pr9 FreeBSD 10 uses clang by default, with gcc not available by default<br>
-- -- 4.02.0dev+trunk latest trunk snapshot<br>
<br>
Each switch corresponds to the current development trunk, with the<br>
diff in the PR applied. If the patch is sane, you can proceed to<br>
install OPAM packages in the experimental tree as usual without<br>
affecting your day-to-day compiler switch.<br>
<br>
Hope this is useful! More details at:<br>
<a href="http://anil.recoil.org/2014/03/25/ocaml-github-and-opam.html" target="_blank">http://anil.recoil.org/2014/03/25/ocaml-github-and-opam.html</a><br>
<br>
It's set to run daily at the moment, and switches will be deleted once<br>
the corresponding pull request is closed.<br>
<br>
cheers,<br>
Anil<br>
<div class="HOEnZb"><div class="h5"><br>
On 30 Jan 2014, at 11:34, Gabriel Scherer <<a href="mailto:gabriel.scherer@gmail.com">gabriel.scherer@gmail.com</a>> wrote:<br>
<br>
> TL;DR: During the six next months, we will follow pull requests (PR)<br>
> posted on the github mirror of the OCaml distribution, as an<br>
> alternative to the mantis bugtracker. This experiment hopes to attract<br>
> more people to participate in the extremely helpful and surprisingly<br>
> rewarding activity of patch reviews.<br>
><br>
><br>
> Dear OCaml community,<br>
><br>
> I think we need more people ready to review patches proposed for<br>
> inclusion in the OCaml compiler/distribution; lack of reviews is<br>
> currently one of the bottleneck in the development process -- among<br>
> others, such as the sheer difficulty to reach consensus on any change<br>
> to the language itself. Doing patch reviews is helpful, extremely<br>
> interesting, and an excellent way to get to know more about small<br>
> parts of the compiler.<br>
><br>
> There was a resurgence of discussions on caml-list (Yotam Barnoy's<br>
> [moving to github] and Adrien Nader's thoughtful proposal of<br>
> a [mailing-list for patch review]). Amir Chaudhry launched a poll to<br>
> record decreasing order of preference, and the [results] are<br>
> clear-cut: people hate Mantis' guts, and would rather use anything<br>
> else.<br>
><br>
> [moving to github]: <a href="http://alan.petitepomme.net/cwn/2013.12.24.html#5" target="_blank">http://alan.petitepomme.net/cwn/2013.12.24.html#5</a><br>
> [mailing-list for patch review]:<br>
> <a href="https://sympa.inria.fr/sympa/arc/caml-list/2014-01/msg00055.html" target="_blank">https://sympa.inria.fr/sympa/arc/caml-list/2014-01/msg00055.html</a><br>
> [results]: <a href="https://docs.google.com/forms/d/1QWhqJRv1yPvdi6E3AiqbvUwlqGorV_Wbk7h_JYuDUiQ/viewanalytics" target="_blank">https://docs.google.com/forms/d/1QWhqJRv1yPvdi6E3AiqbvUwlqGorV_Wbk7h_JYuDUiQ/viewanalytics</a><br>
><br>
> I declare open the following experiment: for six months, starting<br>
> today upto late July, patches proposed for the OCaml distribution may<br>
> be submitted as a pull request (PR) on the [main github mirror], and<br>
> we warmly encourage anyone to review the proposed patches, and make<br>
> any comments they feel can help. Anything that can help improve the<br>
> contribution, or discuss potential issues (backward compatibility,<br>
> future-proofiness of the change, alternative designs...) will speed up<br>
> the time between a patch proposal and a clear decision to integrate it<br>
> or not.<br>
><br>
> [main github mirror]: <a href="https://github.com/ocaml/ocaml/" target="_blank">https://github.com/ocaml/ocaml/</a><br>
><br>
> In six months, we will reconsider, the default choice being to stop<br>
> using github and revert to a mantis-only workflow. In the meantime,<br>
> I will mirror the github PRs on the mantis side, so that contributors<br>
> that do not wish to use the github interface can continue working as<br>
> before. Patches and reviews are of course still welcome on mantis.<br>
><br>
> Note that github will *not* be used for issue tracking, only for patch<br>
> reviews. If you want to submit a patch against a bug discussed in<br>
> Mantis, or want to re-submit a patch already in Mantis (in the wild<br>
> hope of more eyeballs), feel free to send a github PR and link to it<br>
> from the bugtracker. Finally, the github mirror remains *read-only*:<br>
> if patches are accepted, the PR will be closed but will be committed<br>
> to the SVN first, and synced in git as usual.<br>
><br>
> We're just trying things to see if it works better. I hope it does. In<br>
> any case, thanks in advance for your participation -- whichever tool<br>
> you use. Happy hacking!<br>
><br>
> .<br>
><br>
> PS: If you want to get notified for all Pull Requests sent, you<br>
> (need a github account and) can click on the "Watch" button in the top<br>
> right of <a href="http://github.com/ocaml/ocaml" target="_blank">http://github.com/ocaml/ocaml</a> to register for<br>
> notifications. In the [notification settings] page of your account,<br>
> you can set up notifications to get send by email and/or to the<br>
> (mostly useless) github notification web interface.<br>
><br>
> [notification settings](<a href="https://github.com/settings/notifications" target="_blank">https://github.com/settings/notifications</a>)<br>
> _______________________________________________<br>
> Platform mailing list<br>
> <a href="mailto:Platform@lists.ocaml.org">Platform@lists.ocaml.org</a><br>
> <a href="http://lists.ocaml.org/listinfo/platform" target="_blank">http://lists.ocaml.org/listinfo/platform</a><br>
><br>
<br>
_______________________________________________<br>
Platform mailing list<br>
<a href="mailto:Platform@lists.ocaml.org">Platform@lists.ocaml.org</a><br>
<a href="http://lists.ocaml.org/listinfo/platform" target="_blank">http://lists.ocaml.org/listinfo/platform</a><br>
</div></div></blockquote></div><br></div>