<div dir="ltr">I am going to submit feedback right now as well. However, I will say that you can apply the same arguments against defects listed in the release notes as you did with having to use the BST.<div><br></div><div>I.e., Who knows if the Release Notes Author(s) is/are including all of the bugs or leaving some out.</div><div><br></div><div>Also, on the topic of auto-loading content upon scroll...that's a terrible idea for this web tool. It's great for browsing Pinterest...I heard...from a friend.</div><div><br></div><div>Thankfully, Cisco is already working on removing that feature and allowing us to use page numbers instead:</div><div><br></div><div>"Pagination of search results is not supported currently. This functionality will be available in a future release."</div><div>Source: <a href="http://www.cisco.com/web/applicat/cbsshelp/help.html#sort">http://www.cisco.com/web/applicat/cbsshelp/help.html#sort</a></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 6, 2015 at 10:50 AM, Erick Bergquist <span dir="ltr"><<a href="mailto:erickbee@gmail.com" target="_blank">erickbee@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">For example, on the latest UCCX 10.6.1 SU1 release notes they don't<br>
list the caveats fixed and provide a link to the bug search tool. I<br>
sent an email to the feedback link provided in the release notes<br>
document and got an email back this morning from cisco thanking me for<br>
my feedback and explaining their direction and that they will take my<br>
comments into consideration and possibly add a poll. I would advise<br>
others to send feedback using the methods in the documents to share<br>
your opinion with the right people.<br>
<br>
I'm not opposed to using bug search tool for viewing the caveats, it<br>
just doesn't provide a nice list format to view all the resolved/open<br>
caveats with one line summary like in the document.If you scroll down<br>
it keeps updating the display with more bugs so you can't really print<br>
them easily either. And who knows if the search is returning all the<br>
bugs or leaving some out. I also liked seeing the list in the release<br>
notes to compare against bug toolkit results or searching a release<br>
note document for a bug ID to make sure that release indeed included<br>
the fix before applying it on a client/etc.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
Erick<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On Tue, Oct 6, 2015 at 10:17 AM, Justin Steinberg <<a href="mailto:jsteinberg@gmail.com">jsteinberg@gmail.com</a>> wrote:<br>
> The problem is we don't know for sure that the BU is doing that and if we<br>
> review bugtoolkit on monday it could be changed on tuesday. Reviewing<br>
> defects in a release notes file is more assuring.<br>
><br>
> On Tue, Oct 6, 2015 at 10:41 AM, Brian Meade <<a href="mailto:bmeade90@vt.edu">bmeade90@vt.edu</a>> wrote:<br>
>><br>
>> I do agree it's annoying that they're not listed anymore in the release<br>
>> notes. The bright side is at least this forces the BU to make sure all of<br>
>> the resolved/open bugs for that version actually have the correct versions<br>
>> documented in the bug search tool.<br>
>><br>
>> On Tue, Oct 6, 2015 at 8:14 AM, Ryan Huff <<a href="mailto:ryanhuff@outlook.com">ryanhuff@outlook.com</a>> wrote:<br>
>>><br>
>>> #truth<br>
>>><br>
>>> Area that could really be improved<br>
>>><br>
>>> ________________________________<br>
>>> Date: Tue, 6 Oct 2015 07:05:43 -0400<br>
>>> From: <a href="mailto:jsteinberg@gmail.com">jsteinberg@gmail.com</a><br>
>>> To: <a href="mailto:erickbee@gmail.com">erickbee@gmail.com</a><br>
>>> Subject: Re: [cisco-voip] Understanding a Defect's Affected Versions<br>
>>> CC: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
>>><br>
>>><br>
>>> I agree with that. It's too hard to know how to search the bug toolkit<br>
>>> for fixes in a certain version.<br>
>>><br>
>>> On Oct 5, 2015 11:54 PM, "Erick Bergquist" <<a href="mailto:erickbee@gmail.com">erickbee@gmail.com</a>> wrote:<br>
>>><br>
>>> 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<br>
>>> > numbering<br>
>>> > scheme. I thought the ReadMe used to show what ES the SU was built off<br>
>>> > 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<br>
>>> > 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>><br>
>>> > 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<br>
>>> >> > author.<br>
>>> >> > For<br>
>>> >> > UCM you should always assume you are vulnerable if the fixed-in<br>
>>> >> > version<br>
>>> >> > is<br>
>>> >> > higher than what you are currently running unless the bug<br>
>>> >> > 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<br>
>>> >> > 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<br>
>>> >> > 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>
>>><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>
_______________________________________________<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>
</div></div></blockquote></div><br></div>