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 :-]
List view
0 issues of 0 selected
There are no open issues in this milestone
Add issues to milestones to help organize your work for a particular release or project. Find and add issues with no milestones in this repo.