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

11 years ago
11 years ago
  1. Bitcoin integration/staging tree
  2. Development process
  3. ===================
  4. Developers work in their own trees, then submit pull requests when
  5. they think their feature or bug fix is ready.
  6. If it is a simple/trivial/non-controversial change, then one of the
  7. bitcoin development team members simply pulls it.
  8. If it is a more complicated or potentially controversial
  9. change, then the patch submitter will be asked to start a
  10. discussion (if they haven't already) on the mailing list:
  12. The patch will be accepted if there is broad consensus that it is a
  13. good thing. Developers should expect to rework and resubmit patches
  14. if they don't match the project's coding conventions (see coding.txt)
  15. or are controversial.
  16. The master branch is regularly built and tested, but is not guaranteed
  17. to be completely stable. Tags are regularly created to indicate new
  18. official, stable release versions of Bitcoin. If you would like to
  19. help test the Bitcoin core, please contact
  20. Feature branches are created when there are major new features being
  21. worked on by several people.
  22. From time to time a pull request will become outdated. If this occurs, and
  23. the pull is no longer automatically mergeable; a comment on the pull will
  24. be used to issue a warning of closure. The pull will be closed 15 days
  25. after the warning if action is not taken by the author. Pull requests closed
  26. in this manner will have their corresponding issue labeled 'stagnant'.
  27. Issues with no commits will be given a similar warning, and closed after
  28. 15 days from their last activity. Issues closed in this manner will be
  29. labeled 'stale'.
  30. Requests to reopen closed pull requests and/or issues can be submitted to