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.
 
 
 
 
 
 
John Maguire 3b7925eb7d added "Send Bitcoins" option in the tray menu 14 years ago
contrib gitian: strip binaries 14 years ago
cryptopp
doc More 0.3.21 release prep 14 years ago
json
locale
obj
rc
xpm
.gitignore
README.md
base58.h
bignum.h
build-msw.txt
build-osx.txt
build-unix.txt Remove unnecessary line which creates a dependency on wx's png library. 14 years ago
coding.txt
db.cpp
db.h
headers.h
init.cpp Fix segfault when we're unable to create the lock file. 14 years ago
init.h
irc.cpp
irc.h
key.h
license.txt Update date in license.txt 14 years ago
main.cpp Better wording for transaction fee notification messages 14 years ago
main.h Bugfix in recursive check in IsConfirmed() 14 years ago
makefile.mingw
makefile.osx
makefile.unix
makefile.vc
net.cpp
net.h
noui.h
rpc.cpp getbalance '*' was ignoring minconf param. 14 years ago
rpc.h
script.cpp
script.h
serialize.h Bump version number to 0.3.22 14 years ago
setup.nsi Bump version number to 0.3.22 14 years ago
sha256.cpp
strlcpy.h
ui.cpp added "Send Bitcoins" option in the tray menu 14 years ago
ui.h added "Send Bitcoins" option in the tray menu 14 years ago
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.