Not 1.7.  The branch cut + code freeze for each release precedes the actual release by a month or more (as it must, to iron out bugs) and it’s coming up too soon.  For 1.7 my priority is autocast coverage for all high-demand ops that 1.6 missed (RNNs most notably).
1.8 is plausible though.  File an issue on Pytorch github and tag @mcarilli @gchanan @ngimel so we know people want mixed precision training with the C++ API.