v2.16.0(2)
Closed Jan 19, 2018
100% complete
Due to some glitches in the release process, this version was labeled v2.16.0(2) instead of the expected v2.16.0.
So far, this is the only bug in that release, let's cross fingers that it will be the only one :-]
This milestone is closed.
No open issues remain. View closed issues or see open milestones in this repository.