@dmfries724 wrote:
How can version 15.5(3)S be both a known affected release, and a known fixed release?
Good question. I raised this exact question to TAC (different Bug ID) and their response was: The bug was discovered during regression testing and presented back to the developers who, subsequently, corrected the issue.
It is very confusing to non-Cisco staff but that's the new "method" going forward.
My recommendation is raise a TAC Case and get TAC to officially confirm.
Another reason why it is necessary to raise a TAC Case is because details in Bug ID are no longer being updated. Raising a TAC Case will, sometimes, give you some update, like Known Affected Version and/or Known Fixed Versions.
