Litecoin Core integration/staging tree

Go to file

Wladimir J. van der Laan 03b6a1cee4 Merge pull request #3316 `106f133` Fix uninitialized variable added in `b33b9a6fe` (theuni)		11 years ago
contrib	contrib: add sipa's github-merge script	11 years ago
doc	Merge pull request #3275 from Michagogo/release-process-binary-sizes	11 years ago
qa/pull-tester	Update build docs that refer to old makefile.* files.	11 years ago
share	Provide build time when building from tarball:	11 years ago
src	Fix uninitialized variable added in `b33b9a6fe`	11 years ago
.gitattributes	Build identification strings	13 years ago
.gitignore	.gitignore: Simplify references to the same file in different directories	11 years ago
COPYING	Bump version numbers for 0.8 release	12 years ago
INSTALL	Prettify some /Contrib READMEs	11 years ago
Makefile.am	Fix port binding by listening on port $BASHPID	11 years ago
README.md	Documentation Cleanup in /Doc	11 years ago
autogen.sh	autotools: switch to autotools buildsystem	11 years ago
configure.ac	Remove '/': prefix always starts with '/'	11 years ago
pkg.m4	autotools: switch to autotools buildsystem	11 years ago

README.md

Bitcoin 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 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 Bitcoin client software, see http://www.bitcoin.org.

License

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