A good naming convention for software versions!
Click on the blue " Linux " in the upper left corner and select " Set as Star "
Read the useful articles first☞【Dry Goods】Learning Path for Embedded Driver Engineers☞ [Dry Goods] Linux Embedded Knowledge Points - Mind Map - Free Access☞【Employment】Resume template for job search
I wrote an article before about how to automatically generate version numbers.
《 Let your C program automatically print version information 》
The original intention was to allow my program to automatically print version-related information when it is running.
Avoid the problem of some functions not matching due to uncertain version information during testing.
At that time, I left a pit and wrote an article on how to design a relatively standardized version number.
Now fill this hole.
Image version number format
-
project name
Project name, such as YIKOU3568, YIKOU4412
-
firmware version
Software version information, see the next section for details
-
comments
Other descriptive information,
For example, versions of os: Linux, threadx, vxworks , etc.
Or the corresponding hardware platform ap, modem , etc.
Or it can be the id of the last commit on the git server
firmware version detailed format
| name | Format | Length (bytes) | illustrate |
|---|---|---|---|
| v | v | 1 | The image version number starts with v |
| Major | XX | 2 |
Major version number.
For example, 00: engineer sample, 01: feature completion, 02~: commercial release (after commercial release), codebase upgrade or major new feature increment |
| Minor | YY | 2 | Fixing a bug or adding a minor feature, etc. (if the "minor" version is incremented, a release note is required) |
| Build ID | YYMMDD | 7 |
Y: year,
M: month, D: day, N: build number of the day (0, 1, 2...a, b, c...x, y, z) |
| release type | T | 0-1 | T: R&D release test version, official version can be left blank |
Example
For example, the following software versions are to be released:
-
Project name: YIKOU3568,
-
The basic functions of the project have been completed, but it has not yet been officially released commercially.
-
This version fixes some bugs found in the test. The previous minor version was 5.
-
Current date: September 9, 2024,
-
The second compilation of the day,
-
Currently still a beta version: T.
The information is as follows:
-
project name: YIKOU3568
-
Major: 01
-
Monor: 06
-
Build ID: 240909
-
N: 1
-
release type: T
The final version information is as follows:
YIKOU3568_v01.06.2409091_ T
In actual use, you can define the values of individual fields according to your needs.
at last
The published image version number must correspond to the commit of the git server.
When publishing, be sure to delete the local project.
Pull down the latest code from the server,
Then recompile the whole thing.
Then do a rough test.
Make sure there are no issues before releasing the version.
Make sure that each image has a clear commit corresponding to it.
Otherwise, a bug may be found in a certain version.
But I can't find the source code corresponding to this image.
The bug cannot be reproduced on other versions.
The bug cannot be closed.
end
A bite of Linux
Follow and reply【 1024 】 to get a large amount of Linux information
Collection of wonderful articles
Recommended articles
京公网安备 11010802033920号