Litecoin Core integration/staging tree

Go to file

Gavin Andresen e6e87891a9 Windows mingw32 makefile and build notes (thanks m0mchil)		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	Windows mingw32 makefile and build notes (thanks m0mchil)	14 years ago
build-osx.txt	…
build-unix.txt	Explicitly state that make -f makfile.unix is the way to build	14 years ago
coding.txt	…
db.cpp	New RPC command: listaccounts. New RPC setting -rpctimeout. And listtransactions '*'	14 years ago
db.h	New RPC command: listaccounts. New RPC setting -rpctimeout. And listtransactions '*'	14 years ago
headers.h	…
init.cpp	Merge branch show-version-in-help-2 of https://github.com/dooglus/bitcoin	14 years ago
init.h	…
irc.cpp	don't advertise on IRC if we don't allow external connections	14 years ago
irc.h	get external ip from irc	14 years ago
key.h	…
license.txt	…
main.cpp	Reset testnet with a new genesis block	14 years ago
main.h	ReacceptWalletTransactions bugfix	14 years ago
makefile.mingw	Windows mingw32 makefile and build notes (thanks m0mchil)	14 years ago
makefile.osx	…
makefile.unix	…
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	Visual C++ compatibility fixes	14 years ago
rpc.h	…
script.cpp	…
script.h	…
serialize.h	Bump version to 0.3.20.01	14 years ago
setup.nsi	Update windows build process for 0.3.20 release	14 years ago
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	Don't scan the time offsets vector repeatedly once we've displayed the warning that the user's clock may be wrong.	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.