Dash - Reinventing Cryptocurrency
Go to file
Jay Weisskopf aaa468563b Increase resolution of Windows icon.
The .ico file has changed in the following ways:
* Added 64x64 layer (max size for "Classic Mode").
* Added 256x256 layer (max size for Vista and 7).
* Removed copies with no alpha channel:
  * Display depths lower than 32-bits are rare nowadays.
  * 8-bit alpha channels in icons has been supported since XP.
  * If the display depth is lowered, they look no better than the
    downsampled versions that Windows automatically generates.

Tested various sizes on both XP and Win 7. It looks fine
(unchanged) on XP and downright sexy on Win 7.
2011-07-12 20:13:44 -05:00
contrib Enable UPnP by default on bitcoin, but not on bitcoind (on gitian) 2011-07-05 18:21:35 +02:00
doc Added a couple minor things to match newer build process. 2011-07-05 00:59:00 +02:00
locale Compile 'sv' translation 2011-07-08 13:38:24 -04:00
share Increase resolution of Windows icon. 2011-07-12 20:13:44 -05:00
src remove magic number: change threshold for nLockTime to constant 2011-07-09 10:11:28 +02:00
.gitignore Add common temp files to .gitignore. 2011-06-02 20:27:27 -05: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 Updated development process description 2011-01-21 10:52:48 -05: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 development forums: http://www.bitcoin.org/smf/index.php?board=6.0 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 (by who? need people willing to be quality assurance testers), and periodically pushed to the subversion repo to become the official, stable, released bitcoin.

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