Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Bitcoin integration/staging tree
C++ Python C Other

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
cryptopp
json
locale
obj
rc
xpm
README.md
base58.h
bignum.h
build-msw.txt
build-osx.txt
build-unix.txt
coding.txt
db.cpp
db.h
headers.h
init.cpp
init.h
irc.cpp
irc.h
key.h
license.txt
main.cpp
main.h
makefile.mingw
makefile.osx
makefile.unix
makefile.vc
net.cpp
net.h
noui.h
rpc.cpp
rpc.h
script.cpp
script.h
serialize.h
setup.nsi
sha256.cpp
strlcpy.h
ui.cpp
ui.h
ui.rc
uibase.cpp
uibase.h
uint256.h
uiproject.fbp
util.cpp
util.h

README.md

Bitcoin integration/staging tree

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 development forums: http://www.bitcoin.org/smf/index.php?board=6.0 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 they don't match the project's coding conventions (see coding.txt) or are controversial.

The master branch is regularly built and tested (by who? need people willing to be quality assurance testers), and periodically pushed to the subversion repo to become the official, stable, released bitcoin.

Feature branches are created when there are major new features being worked on by several people.

Something went wrong with that request. Please try again.