The story behind the execution of software version numbers

Order:

Recently, Management Center colleague C asked about software version number management, defined the company's software version number rules, and written them into the regulations executed by cmme. C. The three-section rule of the software version number defined by a colleague is recorded as major. minor. (revision). The first major version number major represents the major software version, the second is the minor version number minor represents the software upgrade patch, and the third is an optional segment, the revision code revision is used to express the urgent repair of the software. I agree with the software version number defined by C, and do not agree to use the build number as one of the software versions, because the software development level and management level of our colleagues have not yet achieved the daily build.

With regard to the definition of software version numbers, many colleagues may even notice the version numbers of the software they use even if they have no experience with the software number, but are more or less exposed to the software in their daily work. Or when you are in school, the teacher generally talks about the software version number. However, in my practical work, I found that not many colleagues can understand the software version andSoftware Version NumberAndConfiguration ManagementCombined with application in place.

Case:

At the end of December last year, I checked the system launch process of a project and found that the project team did not use the configuration library. Instead, I obtained different codes from my colleagues' machines. At that time, I was taken aback by my colleagues who performed on-site development in the work environment of the owner. Due to the relocation of the work environment, the connection to the company's code library was interrupted due to public network configuration. As a result, they were unable to check in/out the configuration library to publish the book, and there were bugs in the launch process, and they had to fix it. The management process was hard to imagine!

After the painful launch, after nearly three weeks of stability, I asked the project team to go online again two weeks before the Spring Festival in March, requesting that the latest version be released from SVN, otherwise, we can't believe that the code in the code library is the code that runs in the system. After the Spring Festival, I checked the project team's work. The project team planned to launch the svn code library to ensure that the SVN version and system operating environment were consistent.

I was a little relieved, but my career habits gave me an extra question: "Is there an urgent fix recently ?"

Colleague ll replied: "Yes"

I went on to ask: "is the urgent repair going online from SVN check out ?"

My colleague ll looked at me differently: "We are still developing new versions. If we check out the svn code library, will we not launch the latest unstable code ?"

Reader, after hearing my description, do you see my colleagues understand the problem? Is the software version related to configuration management? How to implement it?

(To be continued)