Kevacoin source tree

Gavin Andresen 344888addd Update date in license.txt		14 years ago
contrib	…
cryptopp	…
json	…
locale	…
obj	…
rc	…
xpm	…
.gitignore	…
README.md	…
base58.h	…
bignum.h	…
build-msw.txt	…
build-osx.txt	build: add note for Snow Leopard users and fix typos in linking instructions	14 years ago
build-unix.txt	…
coding.txt	…
db.cpp	Merge branch 'upnp' of https://github.com/TheBlueMatt/bitcoin	14 years ago
db.h	Automatically rescan after restoring wallet.dat	14 years ago
headers.h	…
init.cpp	Automatically rescan after restoring wallet.dat	14 years ago
init.h	…
irc.cpp	…
irc.h	…
key.h	…
license.txt	Update date in license.txt	14 years ago
main.cpp	Monitor incoming transactions for spends by (a copy of) your own wallet	14 years ago
main.h	Merge branch 'listimmature' of /Users/gavin/src/gavin_btc	14 years ago
makefile.mingw	…
makefile.osx	…
makefile.unix	…
makefile.vc	…
net.cpp	Fix for #156 : UPnP segfault when no valid UPnP IGDs are found.	14 years ago
net.h	…
noui.h	…
rpc.cpp	getbalance '*' was ignoring minconf param.	14 years ago
rpc.h	…
script.cpp	…
script.h	…
serialize.h	…
setup.nsi	…
sha256.cpp	…
strlcpy.h	…
ui.cpp	Ensure version number->string conversion is consistent	14 years ago
ui.h	…
ui.rc	…
uibase.cpp	…
uibase.h	…
uint256.h	…
uiproject.fbp	…
util.cpp	Merge branch 'master' of https://github.com/gjs278/bitcoin	14 years ago
util.h	Merge branch 'master' of https://github.com/gjs278/bitcoin	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.