Community driven twister-core
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Matt Giuca 84711b18bc build-unix.txt: Updated (now OK to use wxWidgets > 2.9.0). 14 years ago
cryptopp
json
locale
obj
rc
xpm
README.md
base58.h
bignum.h
build-msw.txt Windows mingw32 makefile and build notes (thanks m0mchil) 14 years ago
build-osx.txt
build-unix.txt build-unix.txt: Updated (now OK to use wxWidgets > 2.9.0). 14 years ago
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 Windows mingw32 makefile and build notes (thanks m0mchil) 14 years ago
makefile.osx
makefile.unix makefile.unix: Fixed errors building bitcoind without wxWidgets installed. 14 years ago
makefile.vc Update windows build process for 0.3.20 release 14 years ago
net.cpp Set maxconnections default to 125 14 years ago
net.h
noui.h
rpc.cpp Merge branch 'master' of https://github.com/sandos/bitcoin into sandos-master 14 years ago
rpc.h
script.cpp
script.h
serialize.h Bump version to 0.3.20.02 14 years ago
setup.nsi Changed setup for mingw toolchain 14 years ago
sha256.cpp
strlcpy.h
ui.cpp remove From/Message fields from SendDialog 14 years ago
ui.h remove From/Message fields from SendDialog 14 years ago
ui.rc
uibase.cpp remove From/Message fields from SendDialog 14 years ago
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.