SOFTWARE RELEASE PROCEDURE
Lead Author, Integrated Solutions
Approved By & Effective on Date of Signature Below:
Yufen Chang Yu, Integrated Solutions
THIS DOCUMENT IS TO BE REGARDED AS THE OFFICIAL SOFTWARE RELEASE PROCEDURE WITHIN Integrated Solutions. IT IS TO BE MAINTAINED UNDER CHANGE CONTROL BY THE DOCUMENT CONTROL COORDINATOR.
TITLE: Software Release Procedure
DESCRIPTION OF CHANGE
· Draft Issue.
1. Software Distribution
This section outlines the process of software distribution during the various phases of Integrated Solutions development and maintenance. The strategy will be to use the same mechanisms for packaging, distribution control and installation during all phases. The steps can be summarized as follows:
1.1 Software Packaging Procedure
The initial asset delivery will include:
. Application packages
. Release letter
. Installation instructions
. Associated documentation
1.2 System Test Items
The following items complete the list of entrance criteria which must be supplied with each delivery:
. System test plan
. System test case listing
. System test status report
. System test conclusion notes
1.3 Naming Conventions
Integrated Solutions is expected that emergency releases to fix severity 1 & 2 MRs will need to be installed on the Integration Test (IT) machines without the delay of a complete build and some of the other entrance criteria. In these cases, individual modules may be sent directly to the Integrated Solutions release coordinator for installation on the desired machine(s). When successful, it is understood that all emergency patch release will be incorporated in the next scheduled release. The following process is defined for emergency releases going to a customer site. If the emergency release will only be installed in Integrated Solutions then the following requirements can be waived with the approval of the software release coordinator.
An emergency release is defined as a customer required release containing only fixes for severity 1 or 2 MRs.
Emergency releases or patch releases may be required to fix high severity MRs found in the customer environment. Such fixes are usually needed on site as quickly as possible. The following procedure outlines the steps needed to deliver a patch or emergency release to the customer. The customer may request that some of the steps be omitted so that they can expedite delivery.
1.3.2 Process Steps
220.127.116.11 Release Contents
The contents of any patch release and target delivery date will be determined by the Integrated Solutions MR Review Board (MRRB). Customer participation is expected in the MRRB process. The target customer environment (release level) will also be determined at this time as will the regular release in which the patch MRs will be included.
The MRRB will publish the patch release information to the customer, the involved asset teams and the release coordinators as soon as the delivery date and contents are determined.
18.104.22.168 Asset Team
Integrated Solutions will deliver the release after testing it in their own environment. The release will include the following required items:
. Complete release notes including
- List of MRs
- Asset test report
- List of modules (file ownership, file mode, checksums, etc.)
- Execution environment, platform version
- Installation instructions
. Test case(s) for Integrated Solutions regression test
. Installation script(s) - as required
. Data conversion script(s) - as required
22.214.171.124 Integrated Solutions
Upon receipt of the patch release Integrated Solutions will install the release onto servers running the target environment. Integrated Solutions will test the release using the test case(s) supplied by the asset team(s) as well as other test case, as appropriate.
The integration test team will then package the release for the customer. The release package will include the same items as listed above for the asset team release. Those items will be modified to include installation instructions, tailored for the customer, and a test report.
1.3.3 Customer Verification
The customer will verify that the emergency release fixes the original problem(s).
1.4 Software Distribution
1.5 Repository Structure
The structure of the repository directory will resemble the following:
1.6 Distribution Control and Management
The Integrated Solutions installation administrator will have the responsibility of determining the following:
. The test machine on which the application will be installed
. When the application will accept upgrades and point releases
. Software distribution, installation and management
. User and system administration tasks
established and available for the required testing intervals.
2.0 Release Strategy
This section outlines the product release strategy for the customer. It defines the expectations and responsibilities of the release coordinator. The release coordinator’s function is to provide rapid delivery services of generally available software releases to customers.
2.1 Release Procedures
Upon determination that a new release must go to customer, the following steps must be followed:
2.1.1 Software Release Letter
A software release letter must be compiled by the Integrated Solutions release coordinator from various asset release letters. The release letter must contain the following information:
. Unique version number to identify the delivery
. List of hardware and software dependencies including the version numbers of the operating
system and software packages.
. List of all files delivered
. Description of the features supported in the release and any impacts on application
. List of all MR fixes delivered with the release (if applicable).
. Complete installation instruction and backout procedures.
2.2 Release Procedure Guide
The release coordinator will develop the release procedure guide. This guide will document the procedure to create and deliver the complete customer deliverable. Guide contents will include:
. Customer release letter procedure
. File creation and verification procedures
. Product transmission via the network to customer
. Shipping guidelines
. Record keeping and tracking
2.3 File Release Procedures
This section describes the creation and verification procedures for creating the media. When the Integrated Solutions team is done testing, the lead tester must notify the release coordinator to begin manufacturing. The assets will be written into the release area of the distribution machine. A directory must be created for the customer.
. Steps to be followed in manufacturing the media