Line 1,535:
Line 1,535:
===AidaX===
===AidaX===
+
+
==Version Control==
+
+
There are four options for selecting which version of zynthian to run. The selection is made in webconf's SOFTWARE->Version page.
+
+
[[File:Software version - oram stable.png|thumb|Webconf software version with oram stable selected]]
+
+
Select from the four options in the 'Version' selection box.
+
+
===Stable (oram-2409)===
+
+
Selecting this version will configure zynthian to run the most stable version of the software. Updates are infrequent and extensively tested. This is the default version and is recommended for production use. Only ''point releases'' appear in this software channel. A point release is a stable version, e.g. oram-24090.1 is the firsts stable update after the release of oram-2409.
+
+
After selecting this option, select 'Software Update' to apply changes.
+
+
===Staging (oram)===
+
+
Selecting this version will configure zynthian to run the staging version which is used as a pre-release test version. Staging version ''should'' work with minimal issues but is not fully tested. It is recommended to use this if you want to act as a zynthian tester, testing new features and bug fixes aheand of the next point release.
+
+
After selecting this option, select 'Software Update' to apply changes.
+
+
===Testing (vangelis)===
+
+
Selecting this version will configure zynthian to run the testing version which is used as the main development version. Testing version is under continual development and will change frequently, sometimes breaking or with substantial workflow changes. It is recommended to use this only if you are a developer or wish to contribute to testing bleeding edge developement. The Testing version is generally maintained in a working stage so it ''should'' work most of the time.
+
+
After selecting this option, select 'Software Update' to apply changes.
+
+
===Custom===
+
+
Selecting the ''Custom'' option will, after a few seconds, allow individual selection of each software repository. This provides granular control of the software configuration. Each list contains the stable version, stable point releases, testing version and all developement branches. There are two main usecases for selecting custom:
+
+
* Freezing the software at a specific point release - selecting a point release for each of the repositories will freeze the software at that version and no updates will be advertised in the user interface.
+
* Testing bleeding edge development - a new feature may be developed in a specific development branch which may need to be selected to allow testing. It is highly recommended to avoid using this option unless you have a clear understanding of why it may be necessary, e.g. instructed to do so by a core developer.
+
+
[[File:Software version - custom.png|thumb|Webconf software version with custom selected]]
+
+
After selecting this option, select 'Save' and then 'Software Update' to apply changes.
==Learning Pills==
==Learning Pills==