Managing Software As Data » History » Version 2
Version 1 (Steve Welburn, 2012-08-22 03:25 PM) → Version 2/19 (Steve Welburn, 2012-08-22 03:28 PM)
h1. Managing Software As Data
The same issues as Software for data arise:
* Backing up
* Documentation
However whereas data changes slowly / infrequently software is subject to ongoing changes during a project and the source code 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.
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, issue lists and wikis through its can be hosted on the "Sound Software":http://www.soundsoftware.ac.uk "code repository"::http://code.soundsoftware.ac.uk
The same issues as Software for data arise:
* Backing up
* Documentation
However whereas data changes slowly / infrequently software is subject to ongoing changes during a project and the source code 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.
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, issue lists and wikis through its can be hosted on the "Sound Software":http://www.soundsoftware.ac.uk "code repository"::http://code.soundsoftware.ac.uk