Release

Yedino builds are released by most trusted members of the project and checked by community.

People:

• BLD - a builder (any person who can use Linux Debian), at least 2 of them should be highly trusted (preferably more)
• DEVLEAD - a lead developer with access to code repo https://github.com/yedino/galaxy42/
• DEVUPLOAD - a developer with write access to binary-builds repo https://github.com/yedino/galaxy42-release

Actions:

• DEVLEAD: in src/project.* write the version, update README.txt and changelog file
• DEVLEAD: apply git tag -S for given version
• BLD: do the Gitian build - on a Debian 8 computer (or VM) with at least 20 GB free in /home (so around 35 for entire OS, better 80 if possible)
• • ask which is the newest tag that should be built, in this example it is v0.3.2b-rc2
• • git clone https://github.com/yedino/galaxy42/
• • cd galaxy42 # enter that directory
• • git checkout v0.3.2b-rc2
• • as root do: ./install and select the option to install more tools (e.g. devel2)
• • do ./build-gitian -L image -s , or if you have more then 320 GB of space in /home after deleting any previous ~/var-gitian dirs, then -m option can be faster for some cases
• • copy the results to side
• • repeat but instead option -L use -W (like Windows)
• • copy results
• BLD: if building for Mac OS X then
• • prepare the mac os X sdk file
• • run same command but -M instead -L
• DEVUPLOAD: compare the results from several sources to make sure it's the same binary file
• DEVUPLOAD: add the files to galaxy42-release repo
• DEVUPLOAD: also attach the files to galaxy42 repo as releases tab