Recently, the system has been released frequently, so we have to have a release note for each release. I didn’t pay attention to the uniformity of this release note before, but made the following description according to the actual situation each time.
But I still feel that it is better to make a release note document. In this way, it can be executed according to one specification at a time.
I have roughly listed the following:
First, the official version of the server and client dll released
Every time the official version of the server and client is released, copy the latest dll from the server of the beta version to be released to the FTP of the official version server, and then copy it from the FTP to the server folder for replacement.
Note that a backup must be made before the official version is released. Similarly, the dll to be released by the client should also be copied to the FTP of the official version server, and then overwritten to the folder where the official version client is located.
Second, the official version of the client and server configuration file modification
If a new configuration item is added to the system configuration file, it is necessary to specify whether the configuration item should be added to the configuration file of the client or the server.
If the configuration item is modified, you need to clearly write how to change it.
3. Execute the script of the database
Before publishing, the paths of all scripts that need to be published should be clearly written, and the scripts that need to be executed should be specified in the file, so that scripts that do not need to be executed should not be registered in these files.
It is also necessary to clearly explain the registration in time.
Fourth, the release of the third-party dll that needs to be released
In general, when releasing the official version, we only need to release the system dll, but if there is a third party dll that needs to be released, it needs to be explained separately, such as SAP dll to be added to the server for release, or the client to add All other third-party dlls on the list need to be pointed out separately.
5. Services or small plug-ins that need to be released separately
If a separate service or small plug-in needs to be released when a new official version is released, it must be explained separately. For example, if an SSO service is to be released, it must be explained where the SSO service is deployed and whether the configuration file needs to be changed after deployment. , how to change the configuration file, it must be written, and the attached drawings will explain. If you want to publish a small plug-in, the same is true. It is necessary to explain how to deploy the small plug-in on the server, whether to change the configuration file, and how to modify it. It must be written clearly, and the accompanying drawings are also required.
Reprinted in: https://www.cnblogs.com/kevinGao/archive/2013/02/08/2922929.html