Sorry...too many emails going out at once.
Clarification.
We do try to make public any bug that goes out in shipping code.
...
The idea is that all the bugs we find *and fix before the code is
shipped* should not show up on the outside as it would just dilute the
ones that do make it out in our code that is run in the field.
On 4/8/10 2:16 PM, Rodney Dunn wrote:
We dot try to make public any bug that goes out in shipping code.
We don't catch 100%.
The idea is that all the bugs we find in internal testing before code
ships should not show up outside as it would just dilute the ones that do.
Rodney
On 4/8/10 12:38 PM, Buhrmaster, Gary wrote:
Is it normal to hide all the bugs at Cisco?
If a bug is found in dev-test it is marked as internal and fix is put
in. Later if someone in the field hit the same bug, then it is made
external.
And while "security" bugs might be justified to use that
approach, the default should be on openness, rather than
secrecy once the bug is verified that it can be
encountered by a customer in a valid configuration. It
would save a lot of time (and Cisco support costs) for
those that do check the bug toolkit.
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
