Release checklist » History » Version 16

Chris Cannam, 2014-07-09 05:24 PM

1 1 Chris Cannam
h1. Release checklist
2 1 Chris Cannam
3 1 Chris Cannam
For the process of building and releasing binaries of a C++ Vamp plugin.
4 1 Chris Cannam
5 16 Chris Cannam
||Tick here|
6 16 Chris Cannam
|*Code hygiene*||
7 16 Chris Cannam
|Run the "Vamp Plugin Tester":/projects/vamp-plugin-tester on the plugin, under @valgrind --leak-check=full@ (see "valgrind":http://valgrind.org/), and fix everything it reports||
8 16 Chris Cannam
|*Versioning and tagging*||
9 16 Chris Cannam
|Check that copyright dates are correct and up-to-date||
10 16 Chris Cannam
|If this is a new release of a previously-released plugin, remember to increment the plugin's @getPluginVersion()@ value||
11 16 Chris Cannam
|Tag the repository when you have confirmed that the plugin builds successfully on all target platforms||
12 4 Chris Cannam
13 4 Chris Cannam
h4. Categories and RDF
14 4 Chris Cannam
15 4 Chris Cannam
* Make sure you have a sensible category file (@.cat@)
16 4 Chris Cannam
* Generate an RDF template using the @vamp-rdf-template-generator@ program found in @rdf/generator@ in the Vamp plugin SDK, and edit it to contain correct metadata
17 4 Chris Cannam
18 12 Chris Cannam
h4. Platform builds
19 7 Chris Cannam
20 10 Chris Cannam
* Make sure your _release build_ is built in _release mode_ ! i.e. with optimization turned on.
21 8 Chris Cannam
22 7 Chris Cannam
* Top priority build targets:
23 13 Chris Cannam
** 32-bit Windows
24 13 Chris Cannam
** 64-bit OS/X Intel
25 11 Chris Cannam
** 64-bit Linux, _if_ you are not providing source
26 7 Chris Cannam
27 7 Chris Cannam
* Second-tier build targets:
28 7 Chris Cannam
** 32-bit Linux
29 7 Chris Cannam
** 64-bit Linux
30 7 Chris Cannam
** 32-bit OS/X Intel (or universal binary)
31 7 Chris Cannam
32 1 Chris Cannam
* Third-tier build targets:
33 1 Chris Cannam
** 64-bit Windows (may become higher-priority in future though)
34 13 Chris Cannam
35 13 Chris Cannam
* Test each platform build on the oldest and newest platform releases you intend to support -- e.g. Windows XP and Windows 8; OS/X 10.6 and 10.10.
36 13 Chris Cannam
* Test each build on an installation of the platform that does not have any developer tools installed.
37 7 Chris Cannam
38 1 Chris Cannam
h4. Packaging
39 6 Chris Cannam
40 6 Chris Cannam
* Make sure each package contains at least the following files:
41 6 Chris Cannam
** The plugin library!
42 6 Chris Cannam
** @README@ describing the plugin and how to install and use it, identifying the authors, with a link to a site about it
43 6 Chris Cannam
** @COPYING@ containing the licence for the plugin
44 6 Chris Cannam
** @CITATION@ containing BibTeX of any paper to cite when using the plugin in academic work
45 1 Chris Cannam
* Create the source package using @hg archive@ or equivalent to archive directly from your tagged version
46 5 Chris Cannam
47 5 Chris Cannam
h4. Publicity
48 5 Chris Cannam
49 5 Chris Cannam
* Send details of your plugin's download location and the RDF metadata file to cannam@all-day-breakfast.com for inclusion in "the download page":http://vamp-plugins.org/download.html