forked from hydrogen-music/hydrogen
-
Notifications
You must be signed in to change notification settings - Fork 0
/
DEVELOPERS
78 lines (54 loc) · 2.44 KB
/
DEVELOPERS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
DEVELOPER INFO
==============
TODO FIXME DEPRECATED
MAKING A RELEASE
----------------
Transitioning the code to remove some of the development hooks in
order to make a release has several, easy-to-forget steps. They are:
1. Remove the developer hook for 'version':
a. Near the end of SConstruct, where it has 'extra_version',
remove that.
b. If you are bumping the revision, also do that in SConstruct.
c. Update linux/debian/changelog
2. Remove the 'developer warning': in data/hydrogen.default.conf
change hydrogen_preferences/showDevelWarning to "false".
3. Commit your changes to trunk.
4. Make a tarball of the release (gzipped). Use gzip instead of
bzip2 for the folks on Windows. Tarballs should be named:
+--- Release version
|
| +--- Extra release version info
__|__ _|_
hydrogen-0.9.4-rc2.tar.gz
Example: 'tar -pczf hydrogen-0.9.5.tar.gz hydrogen-0.9.5'
5. If this is an RC release, the following steps are optional.
6. In a clean directory, test build the tarball in as many ways as
you can. Call your friends. Have a party. Be sure to build
packages on as many systems as possible. Be sure to install
and uninstall them, too.
7. Go ahead and build binary packages. Follow the naming convention
for the platform that you're building for.
Linux: hydrogen_0.9.4rc2_distro_arch.pkg
distro: the GNU/Linux distro (e.g. 'lenny' for Debian)
arch: the processor it's built for (e.g. i686)
pkg: the package management system (deb, rpm)
OS X: hydrogen_0.9.4rc2_arch.dmg
(arch is optional if the binary will work on both.)
Windows: hydrogen_0.9.4rc2.exe
8. If the release passes these "internal" tests, tag the
release. Remember, after tagging the release you may not
commit changes to the tag.
git tag -a 0.9.4 -m "Tagging 0.9.4"
9. If this is a major release (e.g. 0.9.4), then make a branch for
maintenance patches for your release. If this is a maintenance
release (e.g. 0.9.4.1) then skip this step.
git branch 0.9.4
git push origin 0.9.4
10. Make announcements.
CODING CONVENTIONS
------------------
Use the 'linux' indention. (i.e. Tabs) Allow extra space within
parentheses, like this:
while( !done ) {
foo();
}