I call Daily: 2.79 because that’s basically what it is: 2.79 before official 2.79 release.
It’s not a “Blender” issue, it’s a Rigify thing. https://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.79/Add-ons#Rigify
You can ignore all the below if you want, I remembered that these builds are for finding>reporting>fixing problems before it becomes the final product. Then saw the report area includes a tag for Add-ons and if nothing else, that’s for reporting add-ons included in Blender, which Rigify definitely counts: I reported it here: https://developer.blender.org/T51928
The rest of this is me talking about 2.79 version, why it’s better and something it’s (currently) doing wrong.
I found out that the DEF-bones, at least for IK, will (in the end) follow the control bone’s rotation axis and not all the other MCH bones, so I can temporarily just correct those bones until (hopefully) it’s fixed.
Unless something significant occurs between now and “official” release, all the old Rigify rigs will be deprecated/unavailable requiring use of the “new” rigs which, excluding the experimental super_chain, are essentially modifications/updates to pitchipoy.
The thing is, the new system has some new options, like Auto-script-linking/Bone Group layer colors/Manual Rig target (name the rig before generation, instead of rig and rig_ui.py).
The rigs also have some new things like enabling/disabling Ik following torso or root, and switching IK between Pole Target (the balls not connected to anything) and the two arrows that you just rotate.
But enough about reasons I think 2.79 Rigify is better than the previous version:
In 2.78- Rigify, bones are generated while keeping the metarig’s bone rolls.
In 2.79+ Rigify, bones are generated using an automated bone-rolls calculation.
This can result in incorrect bone rolls.