Bitcoin Core integration/staging tree

cryptocurrency c-plus-plus cryptography bitcoin p2p

Go to file

Wladimir J. van der Laan 3ab1664594 gitian: build against Qt 4.6 Should make it possible to run the resulting GUI executable on Linux distributions that use Qt 4.6, such as Debian Wheezy and Tails. Builds a mini-SDK for building against Qt 4.6. This includes the headers as well as host utilities such as `lrelease`, `qrc` and `moc`. This speeds up the gitian build a bit - libqt4-dev pulled in a lot of packages, and is no longer needed as this provides a replacement of our own. Note: This does not replace the Qt build with at static library. After this commit we still build dynamically against the system Qt library. The only difference is that compatibility with an older version is maintained. This loses minor GUI functionality (such as setPlaceholderText) but still allows integration into the window management of the host OS, unlike when statically linking.		11 years ago
contrib	gitian: build against Qt 4.6	11 years ago
doc	gitian: build against Qt 4.6	11 years ago
qa	Have pull-tester run the listtransactions.py regression test	11 years ago
share	VERSION obtained from source instead of the previous git tag.	11 years ago
src	qt: Periodic translations update	11 years ago
.gitattributes	Build identification strings	13 years ago
.gitignore	Ignore temporary object files	11 years ago
COPYING	Bump version numbers for 0.8 release	12 years ago
INSTALL	Prettify some /Contrib READMEs	11 years ago
Makefile.am	Have pull-tester run the listtransactions.py regression test	11 years ago
README.md	doc: add note about translations to README.md	11 years ago
autogen.sh	autogen.sh: Stop passing --verbose to autoreconf	11 years ago
configure.ac	build: add an option for enabling glibc back-compat	11 years ago
pkg.m4	autotools: switch to autotools buildsystem	11 years ago

README.md

Bitcoin Core integration/staging tree

http://www.bitcoin.org

What is Bitcoin?

Bitcoin is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin 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 Bitcoin Core software, see http://www.bitcoin.org/en/download.

License

Bitcoin 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 Bitcoin 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 Bitcoin.

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 can be compiled and run (assuming they weren't disabled in configure) with: make check

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 BitcoinPullTester. 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/bitcoin/QA/ for how to create a test plan.

Translations

Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.

Periodically the translations are pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as github pull request because the next pull from Transifex would automatically overwrite them again.