Production release is a very rigorous matter. If a problem occurs in one of the processes, it may cause the release of the version to fail. The release involves development, testing, operation and maintenance, etc. A clear division of labor can ensure the success of a release.
Developer
Developers don't just finish developing the program and everything will be fine. After the development is completed, you need to prepare the jar package, war package, sql footsteps, configuration files and configuration items for the release. At the same time, it is necessary to write the step materials for the release. All materials needed for the release must be prepared. Developers are the forerunners of release.
Operation and maintenance personnel
Operation and maintenance personnel are the patron saint of the production environment and the executor of the release. They follow the developer release steps for release. From the developer's point of view, it is a step-by-step puppet. In fact, this is a prejudice against operation and maintenance personnel. Production delivery accident. For example, CUP is 100%, disk space is full, etc. The first to receive information is the operation and maintenance personnel. They will probably locate the problem first through various linux commands. Then to the developers.
Testers
The tester is the verifier of the success of the release. After the operation and maintenance personnel have completed the release according to the developer's release steps, the testers will appear. He will verify the software process one by one according to the requirements to ensure that there are no errors. It can be said that testers are very important, especially in projects involving money. If there is an incomplete test, it may cause the company to lose property.
The release may also involve equipment personnel, network personnel, etc. Be sure to inform the relevant departments before re-publishing, all coordination, lack of a link may hinder the release.
In the comics, there is a scene where the test data is written dead, indicating that the code is not standardized enough. Good course recommendation, purchase rebate.