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.
751 Commits
13 Branches
234 Tags
576 MiB
 
 
 
 
 
 
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '230b894779'
${ noResults }
Go to file
Jay Weisskopf 230b894779
Set default compression for NSIS installer to LZMA. 		14 years ago
contrib Enable UPnP by default on bitcoin, but not on bitcoind (on gitian) 14 years ago
doc Added a couple minor things to match newer build process. 14 years ago
locale Compile 'sv' translation 14 years ago
share Set default compression for NSIS installer to LZMA. 14 years ago
src remove magic number: change threshold for nLockTime to constant 14 years ago
.gitignore Add common temp files to .gitignore. 14 years ago
COPYING directory re-organization (keeps the old build system) 14 years ago
README directory re-organization (keeps the old build system) 14 years ago
README.md Updated development process description 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.