tools:vcs:index
This is an old revision of the document!
Version control
Versioning and archiving of processing routines
- Why versioning?
- Software is always subject to change – that's why it is called “soft”.
- Routines for data processing and analysis develop, often together with the understanding of the task.
- Reverting to the last version that “just worked” is an (easy) task.
- What should be versioned?
- Basically everthing, from a script for data processing to the final manuscript/thesis/project report
- What are prerequisites for ubiquitious versioning?
- Open file formats allowing for easy versioning (ideally text formats)
- Minimal infrastructure requirements, as met by a distributed version control system
- Possibility to share versioned data with others (via simple-to-use web interfaces)
Beware: Versioning without version numbers is only half the battle.
Which tool to use
Note: This section is clearly opinionated. There are definitely other tools available. However, this is the tool the author recommends from own experience.
git – Everything is local
Wide-spread distributed version control system with excellent support
github.com
Largest development and code-sharing platform, with free accounts
tools/vcs/index.1548709686.txt.gz · Last modified: 2019/01/28 22:08 by till