> On May 15, 2015, at 1:28 AM, CiscoNSP List <[email protected]> wrote: > > Bug is still "private"(i.e. Details not publicly viewable) - but located > here: https://tools.cisco.com/bugsearch/bug/CSCuu32800 > > Can provide SR if needed.
It’s cisco policy that any defect hit by customer in production result in that bug getting a proper release note (RNE) and be flagged so it can be seen on CCO. This should happen within 24 hours. You should tell the TAC engineer their policy. It’s quite common that they don’t know this as they spend most of their time working on configuration related issues vs actual software defects. It’s not uncommon for Cisco to take a long time to fix a defect. I recommend calling your account team and having them contact release operations and PM for the platform and set up a call for you to discuss the business impact. If this halts your ability to purchase/deploy equipment or even operate it, you should make sure to classify it as very dire. You should ask ask about if this will be added to the TCATS or an analysis of the Test Escape. Testing software is very hard and some options make it a complete n*2 testing problem or worse as they are mutually exclusive. Right now we have at least 3 p1 cases open with Cisco that are unresolved and fairly catastrophic in nature. Sometimes the developers can only code so fast, and quite often we find it necessary to teach cisco what SCALE truly means. Multiple people logged in at once is not something they think of (as an example). 2-4 weeks is about as fast as they can reasonably move, so keep that in mind. - Jared _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
