kvazar
/
kevacoin
mirror of https://github.com/kvazar-network/kevacoin.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
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.
948 Commits
29 Branches
232 Tags
129 MiB
 
 
 
 
 
 
Tree: 217208a36d
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '217208a36d'
${ noResults }
Gavin Andresen 217208a36d
Merge pull request #516 from TheBlueMatt/nsisiconfix 		13 years ago
contrib Update gitian build descriptors to produce proper builds. 13 years ago
doc wxWidgets needs to be at least version 2.9.1 because wallet crypto uses ToStdString() which is not in 2.9.0 13 years ago
locale Merge pull request #512 from paraipanakos/master 13 years ago
share Update bitcoin icon to make nsis setup exe deterministic. 13 years ago
src Merge branch 'unique_coinbase' of git://gitorious.org/~Luke-Jr/bitcoin/luke-jr-bitcoin into unique_coinbase 13 years ago
.gitignore ignore stuff 13 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 README.md: word wrap text file 13 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 mailing list: http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development

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, but is not guaranteed to be completely stable. Tags are regularly created to indicate new official, stable release versions of Bitcoin. If you would like to help test the Bitcoin core, please contact QA@Bitcoin.org.

Feature branches are created when there are major new features being worked on by several people.