Software Product Release Process

Software Product release process-general Linux technology-Linux programming and kernel information. The following is a detailed description. Posting: releasing software versions in strict accordance with the software product release process is one of the key processes to establish and improve software product version control and ensure the quality of software products.

Participants in software product release are mainly test owners and BM (Build Master ).


Releasing software versions in strict accordance with the software product release process is one of the key processes to establish and improve software product version control and ensure the quality of software products.

Participants in software product release are mainly test owners and BM (Build Master ).





The procedure for releasing the company's software products is as follows:

1. Prepare for release. Prior to release, all programs freezed will be validated and tested by testers; Check that all bugs registered in the qcs system have been fixed, or the legacy bugs do not affect the use of the system, if a major bug is not solved (the level is must fixed), it cannot be released. Smoke Testing is performed before the program is packaged.

2. The Test director prepares the release product quality report for quality analysis and summarization.

3. Import Source Code and documents to the database. The source code includes database creation scripts (including static data), compiling build scripts, and all source code. The documentation includes requirements, design, and test documents, installation manual, user manual, secondary development manual, product introduction (ppt), use demo, etc.

4. BM package the program and tag the source code and document version.

5. Fill in the release baseline notification and notify relevant personnel. The BM manager audits the release baseline.

6. Create a product release plan on the qcs system, fill in configuration items, and execute the release plan (publish the product ).

7. Upload the package and documentation to the download site.

8. Compile the statement readme.txt (or release note ). The Readme content should include the product version description, Product Overview, file packages and documentation descriptions included in this release, feature descriptions included or added in this release, and remaining issues and impact descriptions; copyright Notice and other matters to be clarified.

9. officially release the notification. Notify development, testing, marketing, and sales departments, and attach product release instructions and product introductions.

10. Follow-up work. After the product is released, some bugs may be found during use. If normal use is not affected, these bugs will be solved when the next version is released. If the bug seriously affects use, you must patch the bug or re-release it according to the process.

11. temporary release. A temporary version may be required for emergency use by developers or users before software products are officially released. This version only includes basic packages and necessary instructions for use. For temporary release, developers and testers should be notified; BM should tag the source code and documents.
After the software product is released, a release baseline is established. All user installation and secondary development must be performed on this baseline. Developers cannot directly check the code compilation from cvs or vss for delivery to users or perform secondary development.