Você não pode selecionar mais de 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.
Gavin Andresen fab7858a35 Document how to build/run unit tests 9 anos atrás
contrib Fix broken config files 9 anos atrás
doc Document how to build/run unit tests 9 anos atrás
share Update bitcoinstrings from core and English source translation file 9 anos atrás
src Use a 64-bit nonce in ping 9 anos atrás
.gitattributes Build identification strings 9 anos atrás
.gitignore .gitignore: add test_bitcoin 9 anos atrás
COPYING Update all copyrights to 2012 9 anos atrás
INSTALL Update build instructions for the new, no-wxwidgets world 10 anos atrás
README directory re-organization (keeps the old build system) 10 anos atrás
README.md Updated readme file with timers. 10 anos atrás
bitcoin-qt.pro re-work optionsdialog to a tabbed UI based on an ui-file 9 anos atrás


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@BitcoinTesting.org.

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

From time to time a pull request will become outdated. If this occurs, and the pull is no longer automatically mergeable; a comment on the pull will be used to issue a warning of closure. The pull will be closed 15 days after the warning if action is not taken by the author. Pull requests closed in this manner will have their corresponding issue labeled ‘stagnant’.

Issues with no commits will be given a similar warning, and closed after 15 days from their last activity. Issues closed in this manner will be labeled ‘stale’.

Requests to reopen closed pull requests and/or issues can be submitted to QA@BitcoinTesting.org.