On Thu, Jan 09, 2014 at 07:43:05PM +0100, Louis Gesbert wrote: > Happy new year everyone ! > > I am putting everything together to release 1.1.1 in the next few days, > which should unlock the release of opam-doc and help package > opam-in-a-box. I am getting through the last few issues tagged for > 1.1.1, postponing what is not either trivial or urgent. > > 1.1.1 features mostly bug-fixes and UI/doc improvements, but also > focuses on improving the API and tools to be a better base for the > platform (functions for opam-doc, interface with tools like opamfu and > opam-installer). Once this is released, there will be more room to > (progressively) merge the stash of deeper changes that I have been > working on in the meantime. > > Please discuss any requests or blockers for 1.1.1 ! The biggest current > issue is probably the upgrade problems with the built-in heuristic, but > there isn't much we can do before the release, and the real solution is > to have aspcud packaged and working on OSX.
Thanks Louis! The solver issue is my last remaining big concern as well before getting 1.1.1 out of the door. It would be very useful to characterise the reason for the failure to see if a quick workaround is possible, since so many users are hitting it. If it's just due to the growing number of packages, perhaps we can add some more constraints to the package descriptions help the solver find a solution more easily? Aside from that, the only other problem I can think of that confused users was the inconsistent 'packages added or removed' display after an opam update. Was that fixed? I couldn't find the live issue. When you have an RC let me know, and I'll run it through it's paces on the various BSDs to make sure that there haven't been any regressions due to the `which` vs `type` changes. -anil _______________________________________________ Platform mailing list [email protected] http://lists.ocaml.org/listinfo/platform
