Official Zetacoin repository
C++ Python C M4 Makefile HTML Other
Clone or download
Pull request Compare This branch is 439 commits ahead, 7963 commits behind bitcoin:master.
Latest commit 7769674 Apr 15, 2018

README.md

Zetacoin Core integration/staging tree

https://www.zetac.org

What is Zetacoin?

Zetacoin is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. Zetacoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Zetacoin Core is the name of open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Zetacoin Core software, see https://www.zetac.org/.

License

Zetacoin Core is released under the terms of the MIT license. See COPYING for more information or see http://opensource.org/licenses/MIT.

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 Zetacoin development team members simply pulls it.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if the code doesn't match the project's coding conventions (see doc/developer-notes.md) or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Zetacoin.

Testing

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run with: qa/pull-tester/rpc-tests.py

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.