From 9e1a71dbf96797238021e2db974cf76c70982ba6 Mon Sep 17 00:00:00 2001 From: Brusk Hamarash Date: Wed, 29 Sep 2021 02:10:42 +0300 Subject: [PATCH] Headers + Versioning --- Software-Development/README.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/Software-Development/README.md b/Software-Development/README.md index 5da4107..4c3bde7 100644 --- a/Software-Development/README.md +++ b/Software-Development/README.md @@ -133,3 +133,25 @@ Unless otherwise specified by the Head of Digital Development, the following doc 5. Release Notes 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. +