ditkrg/guidelines-and-instructions
4
0
Fork 0
mirror of https://github.com/ditkrg/guidelines-and-instructions.git synced 2026-01-22 22:06:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

Headers + Versioning

Browse Source
This commit is contained in:
Brusk Hamarash 2021-09-29 02:10:42 +03:00
parent 600c53d625
commit 9e1a71dbf9
No known key found for this signature in database
GPG Key ID: 509F705341F6504F
1 changed files with 22 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
Software-Development/README.md
View File

@ -133,3 +133,25 @@ Unless otherwise specified by the Head of Digital Development, the following doc
5. Release Notes 5. Release Notes
6. README.md that describes each software code's settings. (Refer to README.md templates for each code base) 6. README.md that describes each software code's settings. (Refer to README.md templates for each code base)
### Acceptance
### Deadlines
### Versioning
We follow the [Semantic Versioning 2.0.0](https://semver.org/) standards to version releases. Accordingly, software applications must be versioned with the following pattern: `MAJOR.MINOR.PATCH.`
#### Releases
Releases must be versioned with the same rules of Semantic Versioning while making sure that each release receives a unique version number.
#### Web Applications
All web applications must be versioned appropriately and conform to the rules of this section. The version number must be displayed on the application's user interface unless it is specified and agreed by the Head of Digital Development Team. Manifest files in the code bases must be updated to reflect the release version.
#### CLI Applications
In case of command line applications, an option must be provided (suggestion –v) to display the version.