-
Notifications
You must be signed in to change notification settings - Fork 4
Release Procedure
The purpose of this document is to identify the steps we should perform each time we make a public release of Integra Live
These steps should be performed from scratch on every new release candidate, even if there have only been trivial changes from a previous release candidate.
From a fresh installation of Integra Live:
- Ensure that the version number in the about box is correct
- Test every menu command on the system menu
- Arrange view: creating, removing tracks and blocks. Creating, editing and removing Envelopes.
- Creating, editing, removing scenes. Setting their modes and keyboard shortcuts. Using the Next scene/prev scene function.
- Module Graph: creating and removing modules, creating and removing module connections, setting attributes using via module properties
- Live View: editing module attributes in live view
- Scripting. Create and execute a script, make sure you can read & write module attributes
- Routing. Create, edit and delete a route a) between module attributes b) control something by midi
- File IO. Create a project, connect some modules, save and open the project. Export and reimport a track. Export and reimport a block. Export and reimport a module. Open saved project by double-clicking the file icon.
- Interoperability. Save a project on Mac, open it on Windows. Save a project on Windows, open it on Mac.
- Block Library. Instantiate all blocks in the system block library. Add a user block to the block library, instantiate it, then remove it.
- Info view. Make sure it generally works, edit an info.
- By now you have probably tested most context menu commands, but for completeness, go through each view that has a context menu, and if there's any command you haven't tried yet, try it. These are the views that currently have context menus: Arrange View, Scripting View, Block Library, Live View, Module Graph, Module Properties, Timeline.
Every time any kind of release is made, the build and optionally the version number should be incremented in the root of the git repository.
The github commit from which the release is made should be tagged using the format: Version-x.x.x.xxxx
If the release is a beta release, the tag format should be: Version-x.x.x.xxxx-beta
An initial beta release should always be uploaded to http://integralive.org/testing
This should be announced "internally" as a beta. Once everyone is satisfied we are ready to release a full release should be made.
Normally several beta releases may be made before full release in order to identify and fix bugs.
A full release should then be uploaded to Sourceforge.
Once the release has been uploaded, it should be downloaded and installed to test that the upload was successful and the file is not corrupted.
The upgrade information file should then be updated with the correct version information
The software should then be announced in the following places:
The announcement text should take the form:
We are delighted to announce the latest release of Integra Live — an interactive audio application for musicians and music education
Integra Live supports Mac OS X 10.6 or later and Windows XP or later. It can be downloaded from the Integra Live website:
http://www.integra.io/integralive
Here's what's new...
- Connect over 60 audio modules from delays to granular synths
- Incorporate live interaction with the routing and scripting panels
- Automate parameters using linear or logarithmic envelopes
- Setup audio "scenes" with keyboard and MIDI triggers
- Add parameter controls to the "live view" for performance
- Share and reuse your work with our integrated file format
Coming soon...
- Write your own Integra Live modules in Pure Data using our module developer SDK
Join the community...
Follow us on Twitter: @integralive
Like us on Facebook: http://www.facebook.com/integra.live