Please stabilize.
Would be nice to move this on to R17, or move to mutli-version installs of erlang (a la Python 2/3). This seems particularly pertinent since R17 made some changes that will be quite long-lived, and R16 is the "old way" most existing projects are built against.
Luis, were you the one who had thoughts separating installs? Is upstream doing anything about it yet?
Also, actually erlang-17 being a big change is a good reason not to start stabilizing it yet, that way we can have stable stuff work with 16.x for now.
(In reply to Dirkjan Ochtman from comment #2) > Luis, were you the one who had thoughts separating installs? Is upstream > doing anything about it yet? Yes, exactly. However, I haven't looked into that issue for some time, but I'm planning to investigate it again during the next week(s). I'm not aware of any upstream efforts, though.
(In reply to Dirkjan Ochtman from comment #3) > Also, actually erlang-17 being a big change is a good reason not to start > stabilizing it yet, that way we can have stable stuff work with 16.x for now. Oh, and I forgot to mention that I'm also supportive of putting R17 stabilization on hold.
Stabilized on alpha. Since wings (dependent bug) is only ~alpha, I went ahead. I also have no problem with dekeywording wings entirely if that's the common consensus. Though as noted on the other bug, the failing version of wings is ancient (1.1.1 vs. 1.5.3 being latest)
Let's stabilize 17.3 in bug 499876, instead.
