Managing Software As Data » History » Version 4
Version 3 (Steve Welburn, 2012-11-13 03:00 PM) → Version 4/19 (Steve Welburn, 2012-11-13 03:00 PM)
h1. Managing Software As Data
The same issues as for data arise:
* Backing up
* Documentation
However, whereas data changes slowly / infrequently, software is subject to ongoing changes during a project. Source code for software usually consists of text files and should therefore be stored in a suitable version control system (e.g. Mercurial, Subversion, git). Additionally, binary releases of software may be created as downloads for a project.
The "Sound Software":http://www.soundsoftware.ac.uk project provides software project management facilities for digital music and audio research including Mercurial version control, downloads, documentation, issue lists and wikis through its "code repository"::http://code.soundsoftware.ac.uk
The same issues as for data arise:
* Backing up
* Documentation
However, whereas data changes slowly / infrequently, software is subject to ongoing changes during a project. Source code for software usually consists of text files and should therefore be stored in a suitable version control system (e.g. Mercurial, Subversion, git). Additionally, binary releases of software may be created as downloads for a project.
The "Sound Software":http://www.soundsoftware.ac.uk project provides software project management facilities for digital music and audio research including Mercurial version control, downloads, documentation, issue lists and wikis through its "code repository"::http://code.soundsoftware.ac.uk