Bulletins

© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 2 of 6
Under the new policy, bug fixes can be expected in any new technology release that is in an active maintenance
state as defined by the standard maintenance and extended maintenance release designator.
Figure 2 shows sample standard maintenance and extended maintenance releases and explains the new policy.
Figure 2. Timelines Showing Planned Release Maintenance Process
Standard Maintenance Release
●
Ideal for latest feature and hardware support
●
12 months of critical fixes for bugs with no operational workaround or business affecting severity 1 and
2 issues
●
6 additional months of critical fix support for network affecting bugs such as Product Security Incident
Report Team (PSIRT) issues (standard Cisco PSIRT policy will take precedence; see
http://www.cisco.com/go/psirt)
●
Release might be safe harbor tested (for more information, see
http://www.cisco.com/en/US/netsol/ns504/networking_solutions_program_category_home.html)
●
Same internal shipping quality criteria as extended maintenance release