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

10 years ago
10 years ago
  1. Starwels integration/staging tree
  2. =====================================
  3. [![Build Status](](
  4. What is Starwels?
  5. ----------------
  6. Starwels is an experimental digital currency that enables instant payments to
  7. anyone, anywhere in the world. Starwels uses peer-to-peer technology to operate
  8. with no central authority: managing transactions and issuing money are carried
  9. out collectively by the network. Starwels is the name of open source
  10. software which enables the use of this currency.
  11. For more information, as well as an immediately useable, binary version of
  12. the Starwels software, see, or read the
  13. [original whitepaper](
  14. License
  15. -------
  16. Starwels is released under the terms of the MIT license. See [COPYING](COPYING) for more
  17. information or see
  18. Development Process
  19. -------------------
  20. The `master` branch is regularly built and tested, but is not guaranteed to be
  21. completely stable. [Tags]( are created
  22. regularly to indicate new official, stable release versions of Starwels.
  23. The contribution workflow is described in [](
  24. The developer [mailing list](
  25. should be used to discuss complicated or controversial changes before working
  26. on a patch set.
  27. Developer IRC can be found on Freenode at #starwels-dev.
  28. Testing
  29. -------
  30. Testing and code review is the bottleneck for development; we get more pull
  31. requests than we can review and test on short notice. Please be patient and help out by testing
  32. other people's pull requests, and remember this is a security-critical project where any mistake might cost people
  33. lots of money.
  34. ### Automated Testing
  35. Developers are strongly encouraged to write [unit tests](src/test/ for new code, and to
  36. submit new unit tests for old code. Unit tests can be compiled and run
  37. (assuming they weren't disabled in configure) with: `make check`. Further details on running
  38. and extending unit tests can be found in [/src/test/](/src/test/
  39. There are also [regression and integration tests](/test), written
  40. in Python, that are run automatically on the build server.
  41. These tests can be run (if the [test dependencies](/test) are installed) with: `test/functional/`
  42. The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, and that unit/sanity tests are run automatically.
  43. ### Manual Quality Assurance (QA) Testing
  44. Changes should be tested by somebody other than the developer who wrote the
  45. code. This is especially important for large or high-risk changes. It is useful
  46. to add a test plan to the pull request description if testing the changes is
  47. not straightforward.
  48. Translations
  49. ------------
  50. Changes to translations as well as new translations can be submitted to
  51. [Bitcoin Core's Transifex page](
  52. Translations are periodically pulled from Transifex and merged into the git repository. See the
  53. [translation process](doc/ for details on how this works.
  54. **Important**: We do not accept translation changes as GitHub pull requests because the next
  55. pull from Transifex would automatically overwrite them again.
  56. Translators should also subscribe to the [mailing list](!forum/bitcoin-translators).