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

Compatibility and Deadlines

Browse Source
This commit is contained in:
Brusk Hamarash 2021-10-02 21:36:37 +03:00
parent 9e1a71dbf9
commit 468e2d82c3
No known key found for this signature in database
GPG Key ID: 509F705341F6504F
1 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
Software-Development/README.md
View File

@ -135,10 +135,26 @@ Unless otherwise specified by the Head of Digital Development, the following doc
### Consistency
Applications must be built in a consistent manner from the perspective of the end-user. In case if the need of an inconsistent behavior may arise, it must be properly communicated by the Head of Software Development Team for an approval. Unapproved inconsistencies are not accepted. This must also be respected when adding new features, making changes and improvements, or fixing bugs to existing applications.
### Compatibility
All software must be backward-compatible by default and must take previous versions into considerations. If this not possible or for some design reasons need to change, an approval from the Head of Digital Development Team must be obtained. Unapproved changes that do not adhere to this principle will be considered a bug.
### Acceptance
### Deadlines
All agreed deadlines must be kept as they are unless it is specified or extended explicitly by the Head of Digital Development Team. <u>Members of the Digital Development Team</u> are not obligated to accommodate for requests for late-term changes in the requirements.
In case if priorities change and the agreed deadlines cannot be met, it must be properly communicated to the Head of Digital Development Team in order to come up with a new agreement.
Each release development must come with a time plan that is approved by the Head of Digital Development Team.
### 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.`
@ -154,4 +170,3 @@ All web applications must be versioned appropriately and conform to the rules of
#### CLI Applications
In case of command line applications, an option must be provided (suggestion –v) to display the version.