Comment 3 for bug 1612240

Ok. If 4.2 has been in limbo since May, it's possible it won't be ready in time for 16.10 release. It's also possible that it will be released, but it will unexpectedly introduce incompatibilities with the current git snapshot. If either of these happens, what is the plan for handling this?