forked from rsnel/i0coin
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Version 0.8.0 release candidate 1 Conflicts: .gitignore COPYING src/bitcoinrpc.cpp src/checkpoints.cpp src/db.cpp src/init.cpp src/main.cpp src/main.h src/makefile.linux-mingw src/makefile.mingw src/net.cpp src/rpcdump.cpp src/rpcmining.cpp src/rpcrawtransaction.cpp src/rpcwallet.cpp src/util.cpp
- Loading branch information
Showing
348 changed files
with
64,484 additions
and
15,022 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,42 +1,82 @@ | ||
|
|
||
| Bitcoin integration/staging tree | ||
| ================================ | ||
|
|
||
| http://www.bitcoin.org | ||
|
|
||
| Copyright (c) 2009-2012 Bitcoin Developers | ||
|
|
||
| What is Bitcoin? | ||
| ---------------- | ||
|
|
||
| Bitcoin is an experimental new digital currency that enables instant payments to | ||
| anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate | ||
| with no central authority: managing transactions and issuing money are carried | ||
| out collectively by the network. Bitcoin is also the name of the open source | ||
| software which enables the use of this currency. | ||
|
|
||
| For more information, as well as an immediately useable, binary version of | ||
| the Bitcoin client sofware, see http://www.bitcoin.org. | ||
|
|
||
| License | ||
| ------- | ||
|
|
||
| Bitcoin is released under the terms of the MIT license. See `COPYING` for more | ||
| information or see http://opensource.org/licenses/MIT. | ||
|
|
||
| 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 the code doesn't | ||
| match the project's coding conventions (see `doc/coding.txt`) or are | ||
| controversial. | ||
|
|
||
| The `master` branch is regularly built and tested, but is not guaranteed to be | ||
| completely stable. [Tags](https://github.com/bitcoin/bitcoin/tags) are created | ||
| regularly to indicate new official, stable release versions of Bitcoin. | ||
|
|
||
| Testing | ||
| ------- | ||
|
|
||
| Testing and code review is the bottleneck for development; we get more pull | ||
| requests than we can review and test. Please be patient and help out, and | ||
| remember this is a security-critical project where any mistake might cost people | ||
| lots of money. | ||
|
|
||
| ### Automated Testing | ||
|
|
||
| Developers work in their own trees, then submit pull requests when | ||
| they think their feature or bug fix is ready. | ||
| Developers are strongly encouraged to write unit tests for new code, and to | ||
| submit new unit tests for old code. | ||
|
|
||
| If it is a simple/trivial/non-controversial change, then one of the | ||
| bitcoin development team members simply pulls it. | ||
| Unit tests for the core code are in `src/test/`. To compile and run them: | ||
|
|
||
| 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 | ||
| cd src; make -f makefile.linux test | ||
|
|
||
| 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. | ||
| Unit tests for the GUI code are in `src/qt/test/`. To compile and run them: | ||
|
|
||
| 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 [email protected]. | ||
| qmake BITCOIN_QT_TEST=1 -o Makefile.test bitcoin-qt.pro | ||
| make -f Makefile.test | ||
| ./Bitcoin-Qt | ||
|
|
||
| Feature branches are created when there are major new features being | ||
| worked on by several people. | ||
| Every pull request is built for both Windows and Linux on a dedicated server, | ||
| and unit and sanity tests are automatically run. The binaries produced may be | ||
| used for manual QA testing -- a link to them will appear in a comment on the | ||
| pull request posted by 'BitcoinPullTester'. See `https://github.com/TheBlueMatt/test-scripts` | ||
| for the build/test scripts. | ||
|
|
||
| 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'. | ||
| ### Manual Quality Assurance (QA) Testing | ||
|
|
||
| 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'. | ||
| Large changes should have a test plan, and should be tested by somebody other | ||
| than the developer who wrote the code. | ||
|
|
||
| Requests to reopen closed pull requests and/or issues can be submitted to | ||
| [email protected]. | ||
| See `https://github.com/bitcoin/QA/` for how to create a test plan. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.