Tree [044e45] master /

File Date Author Commit
contrib 2014-06-15 terracoin terracoin [db4c6e] minor: 346805 checkpoint
doc 2012-12-12 Colin Dean Colin Dean [68cb1c] reformat OS X build instrcs, add 10.8 + Homebrew
share 2013-02-11 Gavin Andresen Gavin Andresen [8269a0] Reimplement click-to-pay links. Add OSX support.
src 2014-06-15 terracoin terracoin [db4c6e] minor: 346805 checkpoint
.gitattributes 2012-04-07 Pieter Wuille Pieter Wuille [a20c0d] Build identification strings
.gitignore 2013-02-24 Peter Todd Peter Todd [32ba00] Add two unittest-related files to .gitignore
BUILD 2014-05-06 terracoin terracoin [120f05] minor: checkpoint added.
COPYING 2013-01-30 Gavin Andresen Gavin Andresen [d38c64] Bump version numbers for 0.8 release
ChangeLog 2014-06-15 terracoin terracoin [db4c6e] minor: 346805 checkpoint
INSTALL 2012-10-26 Terracoin Terracoin [897bbc] [customisation] wip,naming,genesis: initial imp... 2014-05-26 terracoin terracoin [b7b465] minor: doc newline. 2014-06-15 terracoin terracoin [db4c6e] minor: 346805 checkpoint

Read Me


Development process

Developers work in their own trees, then submit pull requests when they think
their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the
terracoin development team members simply pulls it.

Official Bitcoin patches are also regurlarly merged into Terracoin.

Newly developped features and additions are submitted to dev-x.y.z branch,
"x", "y" and "z" (respectively major, minor an build) matching a given Terracoin
milestone at github project page.

When an upcoming milestone is about to be released, code from given "dev-x.y.z"
branch is merged into corresponding "release-x.y.z" branch, for testing.

Upon validation, "release-x.y.z" branch is merged into "master" branch,
tested again, and a new tag is created.

Feature branches ("feature-shortname") may eventually be created when two
or more developpers works on the same task.


Testing and code review is the bottleneck for development; we get more pull
requests than we can review and test. Please be patient and help out, and
remember this is a security-critical project where any mistake might cost people
lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to
submit new unit tests for old code.

Unit tests for the core code are in src/test/. To compile and run them:

cd src; make -f makefile.unix test

Unit tests for the GUI code are in src/qt/test/. To compile and run them:

Unit tests for the GUI code are in src/qt/test/
To compile and run them:
qmake TERRACOIN_QT_TEST=1 -o Makefile.test
make -f Makefile.test


We now accept donations towards development and hosting costs :

TRC: 1LpnJb98gXwdzriYXnMe2qryW5915Ysg9a

BTC: 1JaqW8LyfShWaGRnDptF2rBkyMwYAW1aR2