Bitcoin Core integration/staging tree
Go to file
Matt Corallo 6083295f46 Update bitcoin icon to make nsis setup exe deterministic.
This adds a 32x32 16-bit icon to the bitcoin.ico file.
Though this realistically probably looks worse than the 32-bit
32x32 being displayed on a 16-bit monitor, it makes the nsis
setup exe deterministic in gitian output (go figure) which makes
the slight visual loss for users of very old monitors/computers
worth it.
2011-09-14 10:59:54 -04:00
contrib Update gitian build descriptors to produce proper builds. 2011-09-09 12:35:42 -04:00
doc wxWidgets needs to be at least version 2.9.1 because wallet crypto uses ToStdString() which is not in 2.9.0 2011-09-08 20:50:00 -04:00
locale Merge pull request #512 from paraipanakos/master 2011-09-13 13:21:09 -07:00
share Update bitcoin icon to make nsis setup exe deterministic. 2011-09-14 10:59:54 -04:00
src Merge branch 'unique_coinbase' of git://gitorious.org/~Luke-Jr/bitcoin/luke-jr-bitcoin into unique_coinbase 2011-09-07 10:51:57 -04:00
.gitignore ignore stuff 2011-09-06 13:53:04 -04:00
COPYING directory re-organization (keeps the old build system) 2011-04-23 12:10:25 +02:00
README directory re-organization (keeps the old build system) 2011-04-23 12:10:25 +02:00
README.md README.md: word wrap text file 2011-09-05 23:02:35 -04:00

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.