Bug Fixes. When required, Cisco will make new Software available to Integrator to correct a problem, or provide a network-bootable Software image, as determined by Cisco.
Bug Fixes. Licensee will inform Sun promptly, and no later than it informs any third party, of any bugs identified in the Technology, and to the extent that Licensee elects to correct such bugs, Licensee will make the Source Code of such bug fixes promptly available to Sun free. of all restrictions as they are implemented.
Bug Fixes. All bug fixes shall be handled according to the terms of Section 5.1(d) of this Amendment and the SLA in Exhibit A.
Bug Fixes. For a period of one (1) year from the date of delivery, CAERE will provide to Licensee, at no charge, all bug fixes to the Products which CAERE makes generally available at no charge to its customers.
Bug Fixes. Plumtree shall exercise commercially reasonable efforts to --------- correct any reproducible malfunction of the Software reported to Plumtree by Licensee that prevents the Software from performing in accordance with the operating specifications described in the then current Documentation (a "Bug").
Bug Fixes. If a party makes any bug fix modification(s) to any Developed Technology during the term of this Agreement in order to correct errors in such Developed Technology or to make such Developed Technology operate in accordance with its documentation, such modification(s) shall be promptly provided to the other party, and shall be jointly owned by the parties. Modifications to the Developed Technology to enhance performance, other than bug fixes, shall not be subject to this Sections 3.3.1.
Bug Fixes. For the duration of the Cisco warranty period, Cisco will provide Bug Fixes to Integrator as follows:
4.1.4.1 When required, Cisco will provide new Software to Integrator to correct a problem, or provide a network-bootable Software image, as determined by Cisco.
Bug Fixes. PN shall deliver any bug fixes to the Standard Code on a quarterly basis in the twelve (12) months following the initial [*].
Bug Fixes. Digital River shall fix bugs on the Storefront within the following time frames: (a) “Critical” bugs will be addressed on the highest priority and must be fixed as soon as possible after Digital River receives notice from Symantec or otherwise becomes aware of such bug, whichever is first, (b) “Serious” bugs must be fixed within 24 hours after Digital River receives notice from Symantec or otherwise becomes aware of such bug, whichever is first and (c) “Minor” bugs must be fixed within a reasonable timeframe (given the nature of the bug) after Digital River receives notice from Symantec or otherwise becomes aware of such bug, whichever is first. For purposes of this Exhibit, (x) a “Critical” bug is an issue that disallows the normal operation of the Storefront, is an unacceptable Customer experience, or causes latency on the Storefront as evidenced by an alert generated by Keynote, (y) a “Serious” bug is one that disallows the normal operation of the Storefront but a work-around is available to keep the Storefront functioning properly and (z) a “Minor” bug is any problem on the Storefront other than one falling within the Critical or Serious categories. * Confidential treatment has been requested for portions of this exhibit. The copy filed herewith omits the information subject to the confidentiality request. Omissions are designated as *. A complete version of this exhibit has been filed separately with the Securities and Exchange Commission. Digital River’s commitment to use multiple currencies is outlined below:
Bug Fixes. Arbor shall provide bug fixes in accordance with Comshare's internal standards for responsiveness. Comshare will classify the bugs it reports and Arbor will respond according to the following severities (provided, however, that it shall not be a breach of this Agreement if Arbor's performance is within Comshare's own general actual performance for response to the applicable bug classification):
(1) A severity 1 bug is a debilitating bug that stops a customers's application from running. It should be treated as a "drop everything until it's resolved" situation. Resolutions may include get-arounds (provided they are acceptable to the customer), patch disks, or a formal release if necessary. A severity 1 bug must be resolved within 5 working days of notice. The bug fix shall be included in the next available interim release, and no later than 60 days.
(2) Severity 2 bugs are bugs which need to be fixed, but don't have the degree of urgency associated with a severity 1. These bugs are usually easy to get around or obscure cases discovered internally or by only one or two customers. The bug fix shall be included in the next available major release, and no later than 180 days.
(3) A severity 3 bug is the least serious classification. These bugs are largely annoyances more than problems that get in the way of getting the job done. These are most often cosmetic issues. Severity 3 bugs should be fixed when the affected area of code is next modified, or within one year of notice, whichever is sooner. The fix is then included in the next available major release.
