Software Version Management

Software Version management is often ignored for new employees. This article briefly introduces the classification of software versions and introduces a practical method for managing software versions.

1. Software Version Classification

In actual software development projects, software versions are generally classified according to the two standards.

(1) According to the application scope of the software versionGeneral VersionAndCustom version.

As the name suggests, the general version is suitable for most bureaus (bureaus are also the place where the software is used), and the customized version is developed for a special bureau. Their graphical representation is 1.

Figure 1 graphical representation of general and custom versions

 

(2) According to the coverage scope of the software versionMain versionAndPatch version.

It can be understood that the main version is the road we are taking, and the patch version is the branch on both sides of the road. The patch version is used to solve a problem (such as program bug and optimization) in the main version.

 

As for the naming of software versions, different companies have different conventions, which are not described here. When you get to the company, you will find that some software versions are very interesting.

 

2. A Practical Software Version Management Method

When we first started, we developed a relatively small number of versions, so there is usually no confusion in the software version. As the working hours grow, the number of software versions developed gradually increases. If you do not have good version management habits, problems such as difficult version search and incorrect version submission may occur, it seriously affects work efficiency and version quality.

The following describes a software version management method used by the author.

Assume that there is a software version named "DB-voice v1.01.01", and the program was modified in October 14 and October 15. Put the changed content in a folder named after time (for example, 20141014 and 20141015), as shown in figure 2.

Figure 2 storage status of the modified version every day

Based on the changes made on the current day, create a text file named "modify content", which contains the modified content of the current day for later viewing and summarization. In addition, you can store the modified program Version Content in a folder named "content. 3.

Figure 3 storage of daily versions

The author himself stores the data in days. Of course, you can increase or decrease the storage frequency according to your own situation. You can save the storage frequency every half day or every two days.

 

Software Version Management is a matter of detail, but we can make high-quality software only by completing the details.

 

 

(My microblogging: http://weibo.com/zhouzxi? Topnav = 1 & WVR = 5, No.: 245924426, welcome !)

Software Version Management