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.
Wladimir J. van der Laan 0465c41c84 move current qt specific readme to doc/, restore original README.md 10 years ago
contrib Merge branch 'master' of https://github.com/bitcoin/bitcoin 10 years ago
doc move current qt specific readme to doc/, restore original README.md 10 years ago
locale Merge pull request #512 from paraipanakos/master 10 years ago
scripts/qt move qt-specific scripts to qt-specific directory in scripts/ 10 years ago
share Update bitcoin icon to make nsis setup exe deterministic. 10 years ago
src assure that base bitcoind and bitcoin still build 10 years ago
.gitignore Some Mac OS X specific things 10 years ago
COPYING add the bitcoin (MIT?) license 10 years ago
README directory re-organization (keeps the old build system) 10 years ago
README.md move current qt specific readme to doc/, restore original README.md 10 years ago
bitcoin-qt.pro remove transparency effect and windows-specific code for now, it's not working as supposed 10 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.