Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.
Gavin Andresen 7464e647de Bumped version numbers to 0.4.0rc1 pirms 10 gadiem
contrib Bumped version numbers to 0.4.0rc1 pirms 10 gadiem
doc Bumped version numbers to 0.4.0rc1 pirms 10 gadiem
locale Update binary mos to latest translations. pirms 10 gadiem
share Bumped version numbers to 0.4.0rc1 pirms 10 gadiem
src Bumped version numbers to 0.4.0rc1 pirms 10 gadiem
.gitignore Add common temp files to .gitignore. pirms 10 gadiem
COPYING directory re-organization (keeps the old build system) pirms 10 gadiem
README directory re-organization (keeps the old build system) pirms 10 gadiem
README.md Updated development process description pirms 11 gadiem

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 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.