Kevacoin source tree
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.
 
 
 
 
 
 
Gavin Andresen ae42d69d72 Updated development process description 14 years ago
cryptopp
json
locale
obj
rc
xpm
README.md Updated development process description 14 years ago
base58.h
bignum.h
build-msw.txt
build-osx.txt
build-unix.txt
coding.txt
db.cpp
db.h
headers.h
init.cpp Add -rescan option to --help output 14 years ago
init.h
irc.cpp don't advertise on IRC if we don't allow external connections 14 years ago
irc.h
key.h
license.txt
main.cpp Merge branch '4wayswitch' of https://github.com/dooglus/bitcoin into integration 14 years ago
main.h ReacceptWalletTransactions bugfix 14 years ago
makefile.mingw
makefile.osx
makefile.unix
makefile.vc
net.cpp add -nolisten command line option 14 years ago
net.h
noui.h
rpc.cpp Reconcile getbalance and listaccounts 0 in the shared-wallet case 14 years ago
rpc.h
script.cpp
script.h
serialize.h
setup.nsi
sha256.cpp
strlcpy.h
ui.cpp EndModal fix for Mac from piotrp 14 years ago
ui.h
ui.rc
uibase.cpp don't set statusbar background color 14 years ago
uibase.h
uint256.h
uiproject.fbp don't set statusbar background color 14 years ago
util.cpp Fix bus error in DebugPrint if -datadir given non-existent directory. 14 years ago
util.h add -nolisten command line option 14 years ago

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.