Software Release Sample Clauses

Software Release. A complete or partial delivery of software implemented at TTG’s discretion that updates all or some portion of the Software or serves as the basis for a Modification, Improvement or Enhancement and resides on the servers at the TTG Dallas facility.
AutoNDA by SimpleDocs
Software Release. Most recent revision of the EIMS Software.
Software Release. A Software Release is a new version of Software that contains new Standard Features, O/SS upgrades, and those Optional Features that have been licensed separately and individually by Clearwire. Standard Features. Standard Features are included in the current Software Release at no additional charge. Included in the Standard Features is the Call Processing functionality that allows the Network Elements to operate as a wireless communications system. Subscriber Features. Subscriber Features are those that can either be offered on a per-subscriber or per-traffic channel basis and/or which are apparent as features to the subscriber. Examples of Subscriber Features include Caller Preview Service, Message Waiting Notification and Authentication.
Software Release. A complete or partial delivery of one or more TTG Products, normally on magnetic media, but may be transmitted electronically, at TTG’s discretion. There are several kinds of Software Releases as listed below:
Software Release. A supported version of Software published in accordance with a product roadmap and release schedule. Support Period: the period of time during which Azenta will perform Support Services for Customer Support Request: request made by the Customer in accordance with this schedule for support in relation to the Software or Documentation. Support Services: maintenance and provision of supported versions and releases of the Software, including Help Desk Support, but excluding any Out-of-Scope Services. All other capitalized terms in this schedule shall have the meaning given to them in the Main Agreement.
Software Release. The release cycle of the software developed by the project (called gCube) includes several tasks: integration, packaging, testing, distribution, etc. The orchestration of the different activities associated to these tasks is based on the release cycle procedure. This procedure is described in detail in the “SA3 Software Integration, Testing and Distribution” work package wiki page: xxxxx://xxxxxxx.xxxx.x0xxxxxxx-xx.xxxxxxxx- xxxxxxxxxxxxxxx.xx/xxxxxxx/xxxxx.xxx/Xxxxxxxxx_Xxxxxxx_Xxxxx
Software Release. ICT Networks will make available Software Releases and applicable Documentation, if any, to Customer as such releases become generally commercially available. Each Software Release will include a written description of the changes included in such release, and such description will also include a discussion of the purpose or reason for releasing the Software Release. Every Software Release will be accompanied by written installation instructions.
AutoNDA by SimpleDocs
Software Release. At Customer's request, Seller will provide: (a) current list of compatible hardware operating system releases; and (b) a list of Seller's Software Supplemental or Standard Releases.
Software Release. Juniper Networks will make available Software Releases and applicable Documentation, if any, to Customer as such releases become generally commercially available. Each Software Release will include a written description of the changes included in such release, and such description will also include a discussion of the purpose or reason for releasing the Software Release. Every Software Release will be accompanied by written installation instructions.
Software Release. Software Partner agrees to withhold advertising Mississippi’s acceptance of software, and will not accept Mississippi returns, until Mississippi certification is complete. By signing this document, the software partner promises Mississippi that they will have completed their Self-Assessment prior to processing any Mississippi returns. Signature of Authorized Representative Title Date Print Name Date Assessment Completed (or will be completed) Name of Risk Officer Email Address Phone Number A completed and signed agreement must be received by the department by October 30, 2015 in order for the software to be certified for tax year 2015. Answers to the questions in Section III C 4 should be attached.
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!