On Tue, 25 Nov 1997, Robert Fournerat wrote: > Robert Tranter wrote: > > > > I think that everyone is missing the larger point with the patch release > > issue. Rather than getting Ascend to test the patch releases better, we > > need to get them to test the full releases better. Why should it that 34 > > patches to the 5.0 release to get most of their advertised features to > > function at a basic level. As far as I am aware, HDLC issues are > > stilloutstanding, OSPF still does not work, and we cannot get modem code > > that remains stable from patch to patch. > > > > So we all buy the same old line from Ascend about supporting complex > > systems and that if we can just wait for the next patch/incremental/full > > release all of our problems will be solved. I have had Ascend equipment > > since November of 1995. That tune has gotten really old over two years. > > So I await release 6.0 of the code to fix functionality sold to me 2 > > years ago. Any one want ot bet on how many patches it takes in 6.0 to > > fix OSPF, HDLC, etc.? > > > > I very much agree with the 2nd paragraph. Agreed, I think we all can agree to the above. > > I would like to see Ascend publish their formal test procedures > for the p and i releases of each product. I would also like to > see Ascend publish the test results in some easy to read, tabular > format, and a detailed format. This way I should know what they > did or didn't test, and could use this information to help determine > if I should upgrade equipment... Would it help? Honestly, Items have "slipped" though their regression testing many times, Items that I'm sure were "tested", It would just make me a whole hell of a lot madder if I saw for instance radius accounting is broken, Then I see Radius Accounting ****** Test Passed Only way to ensure that the items that we have seen lately don't make it pass the regression test is re-do all the procedures and policy, Start over. > > I imagine that we users could make suggestions of scenarios to add > to their test suite. The TAC team I spoke of before would help. Get out in the enviroments and see exactley what we (The ISPS) are doing with your equipment. > > Am I the only one who thinks this is part of a normal software > QA regimen for production software? Nope. > > Robert Jason Nealis Director Internet Operations Network Access Erols Internet ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.nealis.net/ascend/faq">http://www.nealis.net/ascend/faq</A>> </PRE> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <!--X-Follow-Ups-End--> <!--X-References--> <HR> <STRONG>References</STRONG>: <UL> <LI><STRONG><A HREF="msg11007.html">Re: (ASCEND) Re: 5.0Ap34</A></STRONG></LI> <UL> <LI><EM>From</EM>: Robert Fournerat <robert@netin.com></LI> </UL> </UL> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg11032.html">Re: (ASCEND) fatal error index 2</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg11030.html">RE: (ASCEND) BGP 4 ? (fwd)</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg11007.html">Re: (ASCEND) Re: 5.0Ap34</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg10986.html">(ASCEND) pipe 50 password reset</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="maillist.html#11031"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd250.html#11031"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>