Just an update on the 1.6.10/11 situation. 1.6.10 is dead-on-arrival, thanks to some interesting bugs found as a result of the issue #3242 work. Mike and Paul continue to troubleshoot that, but the idea has been floated that we release 1.6.11 within the next couple of days, *without* those fixes, and then push a 1.6.12 when those fixes become available. Depending on the time required (Mike and Paul can hopefully give a status update on this), I'm inclined to follow this path.
However, 1.6.x is not currently in a releasable state, with the swig-rb test still failing, as well as a basic test on Windows. Fixes for both have been identified, and are under discussion. Thoughts? -Hyrum
