netcraft
/
litecoin
mirror of https://github.com/litecoin-project/litecoin
6
0
Fork 0
Code Issues Projects Releases Wiki Activity
Litecoin Core integration/staging 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.
518 Commits
13 Branches
234 Tags
576 MiB
 
 
 
 
 
 
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'a584320357'
${ noResults }
Go to file
Jeff Garzik a584320357
Ensure version number->string conversion is consistent 		14 years ago
contrib move gitian descriptor file 14 years ago
cryptopp
…
json
…
locale Allow UPnP mapping when USE_UPNP is defined and miniupnpc is installed at build time(statically linked). 14 years ago
obj
…
rc
…
xpm
…
.gitignore Added .gitignore, which prevents 'bitcoin' and 'bitcoind' from showing up in git. 14 years ago
README.md Updated development process description 14 years ago
base58.h
…
bignum.h
…
build-msw.txt Allow UPnP mapping when USE_UPNP is defined and miniupnpc is installed at build time(statically linked). 14 years ago
build-osx.txt Allow UPnP mapping when USE_UPNP is defined and miniupnpc is installed at build time(statically linked). 14 years ago
build-unix.txt Allow UPnP mapping when USE_UPNP is defined and miniupnpc is installed at build time(statically linked). 14 years ago
coding.txt
…
db.cpp Merge branch 'upnp' of https://github.com/TheBlueMatt/bitcoin 14 years ago
db.h
…
headers.h
…
init.cpp Ensure version number->string conversion is consistent 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 New checkpoint at block 118,000 14 years ago
main.h Merge branch 'listimmature' of /Users/gavin/src/gavin_btc 14 years ago
makefile.mingw Allow UPnP mapping when USE_UPNP is defined and miniupnpc is installed at build time(statically linked). 14 years ago
makefile.osx Allow UPnP mapping when USE_UPNP is defined and miniupnpc is installed at build time(statically linked). 14 years ago
makefile.unix Allow UPnP mapping when USE_UPNP is defined and miniupnpc is installed at build time(statically linked). 14 years ago
makefile.vc Update windows build process for 0.3.20 release 14 years ago
net.cpp Merge branch 'upnp' of https://github.com/TheBlueMatt/bitcoin 14 years ago
net.h Allow UPnP mapping when USE_UPNP is defined and miniupnpc is installed at build time(statically linked). 14 years ago
noui.h
…
rpc.cpp Merge branch 'listimmature' of /Users/gavin/src/gavin_btc 14 years ago
rpc.h
…
script.cpp
…
script.h
…
serialize.h Bump version number to 0.3.21 (lest we forget) 14 years ago
setup.nsi Changed setup for mingw toolchain 14 years ago
sha256.cpp
…
strlcpy.h
…
ui.cpp Ensure version number->string conversion is consistent 14 years ago
ui.h remove From/Message fields from SendDialog 14 years ago
ui.rc
…
uibase.cpp Allow UPnP mapping when USE_UPNP is defined and miniupnpc is installed at build time(statically linked). 14 years ago
uibase.h Allow UPnP mapping when USE_UPNP is defined and miniupnpc is installed at build time(statically linked). 14 years ago
uint256.h
…
uiproject.fbp Allow UPnP mapping when USE_UPNP is defined and miniupnpc is installed at build time(statically linked). 14 years ago
util.cpp Ensure version number->string conversion is consistent 14 years ago
util.h Ensure version number->string conversion is consistent 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.