requirements:versioning:index
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
requirements:versioning:index [2019/01/28 23:01] – till | requirements:versioning:index [2020/09/29 16:16] (current) – till | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{fa> | + | {{fa> |
+ | ====== Versioning ====== | ||
// | // | ||
+ | <WRAP group> | ||
+ | <WRAP column 32px> | ||
+ | <WRAP column 85%> | ||
* Routines used for processing and analysis need to have unique version numbers. | * Routines used for processing and analysis need to have unique version numbers. | ||
- | * The code should be open-source and stored in a version control system (VCS) to allow for reproducibility of the exact step with the exact same code. | + | * The code should be open-source and stored in a version control system (VCS)\\ to allow for reproducibility of the exact step with the exact same code. |
* The versions need to be long-term archived, similarly for decades as the data. | * The versions need to be long-term archived, similarly for decades as the data. | ||
+ | </ | ||
+ | </ | ||
+ | As mentioned when discussing [[..: | ||
+ | |||
+ | Furthermore, | ||
+ | |||
+ | Eventually, the routines and all their versions need to be **long-term archived**, for a similar time frame as the original data. For furhter discussion of the requirements of long-term storage, see the [[..: | ||
+ | |||
+ | |||
+ | \\ | ||
+ | <WRAP half column leftalign>< | ||
+ | <WRAP half column rightalign>< | ||
requirements/versioning/index.1548712915.txt.gz · Last modified: 2019/01/28 23:01 by till