<p dir="ltr">I agree with that. It's too hard to know how to search the bug toolkit for fixes in a certain version. </p>
<div class="gmail_quote">On Oct 5, 2015 11:54 PM, "Erick Bergquist" <<a href="mailto:erickbee@gmail.com">erickbee@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm also not a fan of the newer release notes not including a list of<br>
the Resolved Bugs, but a link to bug search tool...<br>
<br>
That leaves it up to us to find what bugs were fixed or hoping bug<br>
search tool returns them all, plus not a nice list/summary to glance<br>
through.<br>
<br>
On Mon, Oct 5, 2015 at 10:47 PM, Brian Meade <<a href="mailto:bmeade90@vt.edu">bmeade90@vt.edu</a>> wrote:<br>
> 10.5.2.12028-1 is an Engineering Special which uses a different numbering<br>
> scheme. I thought the ReadMe used to show what ES the SU was built off of<br>
> but having trouble finding it.<br>
><br>
> SU2/SU2a were most likely built off of older engineering specials than<br>
> 10.5.2.12028-1.<br>
><br>
> The higher release thing really only works in the case of published versions<br>
> on <a href="http://cisco.com" rel="noreferrer" target="_blank">cisco.com</a>.<br>
><br>
> On Mon, Oct 5, 2015 at 11:34 PM, Erick Bergquist <<a href="mailto:erickbee@gmail.com">erickbee@gmail.com</a>> wrote:<br>
>><br>
>> Some bugs, like CSCuu58142 effecting single number reach doesn't seem<br>
>> to follow higher versions contain the fix methodology.<br>
>><br>
>> Bug toolkit says this is fixed in 10.5.2.12028-1 but 10.5.2 SU2, SU2a<br>
>> (10.5.2.12900 and 10.5.2.12901) don't contain the bug fix per TAC and<br>
>> going over the release notes for SU2, SU2a.<br>
>><br>
>> I need to use the 10.5.2.12028-1 ES or latest ES 10.5.2.13039-1.<br>
>> Currently debating which route I'm going to go or wait out for SU3 or<br>
>> until we upgrade to 11.x. This SNR bug is effecting some users about<br>
>> every 1-2 months. Workaround is to disable SNR on their remote<br>
>> destination profile and re-enable it.<br>
>><br>
>><br>
>><br>
>> On Tue, Sep 29, 2015 at 2:03 PM, Ryan Ratliff (rratliff)<br>
>> <<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>> wrote:<br>
>> > it's up to the discretion of the bug author. <--------------<br>
>> ><br>
>> ><br>
>> > This means it’s accuracy varies greatly by product and even bug author.<br>
>> > For<br>
>> > UCM you should always assume you are vulnerable if the fixed-in version<br>
>> > is<br>
>> > higher than what you are currently running unless the bug description<br>
>> > clearly states otherwise or the feature impacted by the bug doesn’t<br>
>> > exist in<br>
>> > your version.<br>
>> ><br>
>> > -Ryan<br>
>> ><br>
>> > On Sep 29, 2015, at 2:25 PM, Anthony Holloway<br>
>> > <<a href="mailto:avholloway%2Bcisco-voip@gmail.com">avholloway+cisco-voip@gmail.com</a>> wrote:<br>
>> ><br>
>> > In reference to this defect:<br>
>> ><br>
>> > <a href="https://tools.cisco.com/bugsearch/bug/CSCuv45722" rel="noreferrer" target="_blank">https://tools.cisco.com/bugsearch/bug/CSCuv45722</a><br>
>> ><br>
>> > Can you help me understand what this means as far as all affected<br>
>> > versions?<br>
>> ><br>
>> > On the surface, it would appear that it's only affecting 9.1(2).<br>
>> > However,<br>
>> > with a fixed in version being way out in 11.5, that would also indicate<br>
>> > to<br>
>> > me that an upgrade to 10.5(2)SU2a, as an example, would not fix this<br>
>> > issue.<br>
>> ><br>
>> > Does Cisco imply all versions affected between the listed affected<br>
>> > versions<br>
>> > and the fixed in version? Or, should this defect list all affected<br>
>> > versions?<br>
>> ><br>
>> > I cannot recall what I've heard about this in the past. I'm almost<br>
>> > guessing<br>
>> > there's no exact science to it, and it's up to the discretion of the bug<br>
>> > author.<br>
>> ><br>
>> > Thanks for your help.<br>
>> > _______________________________________________<br>
>> > cisco-voip mailing list<br>
>> > <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
>> > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > cisco-voip mailing list<br>
>> > <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
>> > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
>> ><br>
>> _______________________________________________<br>
>> cisco-voip mailing list<br>
>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div>