Menu

Tree [aa416f] master /
 History

HTTPS access


File Date Author Commit
 contrib 2015-05-29 metrospark metrospark [e504ee] Updated JET links
 db 2013-11-26 Wladimir J. van der Laan Wladimir J. van der Laan [83efc9] Squashed 'src/leveldb/' changes from be1b0ff..b...
 doc 2015-05-29 metrospark metrospark [df0de3] JET Genesis
 share 2015-05-29 metrospark metrospark [e504ee] Updated JET links
 src 2015-05-29 metrospark metrospark [df0de3] JET Genesis
 .gitattributes 2012-04-07 Pieter Wuille Pieter Wuille [a20c0d] Build identification strings
 .gitignore 2015-05-29 metrospark metrospark [df0de3] JET Genesis
 COPYING 2013-01-30 Gavin Andresen Gavin Andresen [d38c64] Bump version numbers for 0.8 release
 INSTALL 2015-05-29 metrospark metrospark [df0de3] JET Genesis
 README.md 2015-06-01 Marlon Hanks Marlon Hanks [aa416f] Update README.md
 bitcoin-qt.pro 2015-05-29 metrospark metrospark [df0de3] JET Genesis

Read Me

Jetcoin integration/staging tree

https://jetcoin.org

What is Jetcoin?

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

For more information, as well as an immediately useable, binary version of
the Jetcoin client software, see https://jetcoin.org.

License

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

If it is a more complicated or potentially controversial change, then the patch
submitter will be asked to start a discussion (if they haven't already) on the
mailing list.

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/coding.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 Jetcoin.

Testing

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:

qmake BITCOIN_QT_TEST=1 -o Makefile.test jetcoin-qt.pro
make -f Makefile.test
./jetcoin-qt_test

Every pull request is built for both Windows and Linux on a dedicated server,
and unit and sanity tests are automatically run. The binaries produced may be
used for manual QA testing — a link to them will appear in a comment on the
pull request posted by JetcoinPullTester. See https://github.com/TheBlueMatt/test-scripts
for the build/test scripts.

Manual Quality Assurance (QA) Testing

Large changes should have a test plan, and should be tested by somebody other
than the developer who wrote the code.

See https://github.com/jetcoin/QA/ for how to create a test plan.

Copyright (c) 2009-2013 Bitcoin Developers

Copyright (c) 2014-2015 Treefunder Incorporated