[c-nsp] how not to write a release note
Kevin Graham
kgraham at industrial-marshmallow.com
Tue Nov 17 14:45:20 EST 2009
> Does not say anything about what may trigger it, eg: mtu,
> packet fragmentation, etc..
Though that one is higher profile, still not as bad as:
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/csm/4.2.x/release/notes/ol_6897.html#wp274407
...listed as a "Limitation and Restriction" (as opposed to "Open
Caveat") with no bug citation.
At least there's some good bug release-note authors out there,
as evidenced byCSCse14048:
Cisco X2-10GB-LR transceiver modules with a
version
identification number lower than V03 might show
intermittent
frame check sequence (FCS) errors or be
ejected from the switch during
periods of operational
shock greater than 50g. There is no workaround.
(still waiting to be able to recommend that as a possible
problem to a c-nsp poster...)
More information about the cisco-nsp
mailing list