twisterarmy
/
twister-core
mirror of https://github.com/twisterarmy/twister-core.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Community driven twister-core
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.
1989 Commits
3 Branches
17 Tags
21 MiB
 
 
 
 
 
 
Tree: b0a7e05a45
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'b0a7e05a45'
${ noResults }
Pieter Wuille b0a7e05a45
Merge pull request #1019 from laanwj/2012_03_uirefactor 		13 years ago
contrib Merge pull request #934 from luke-jr/gitian_luke 13 years ago
doc updated translation process documentation 13 years ago
scripts/qt move qt-specific scripts to qt-specific directory in scripts/ 13 years ago
share Bump version to 0.6.0.99 for 0.6.1 merge window 13 years ago
src Merge pull request #1019 from laanwj/2012_03_uirefactor 13 years ago
.gitignore Output build temp files in build/ instead of current directory. 13 years ago
COPYING Update all copyrights to 2012 13 years ago
INSTALL Update build instructions for the new, no-wxwidgets world 13 years ago
README directory re-organization (keeps the old build system) 14 years ago
README.md Updated readme file with timers. 13 years ago
bitcoin-qt.pro Move from noui.h / ui.h to one ui_interface.h with dummy implementation for the daemon. 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@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.