Dash - Reinventing Cryptocurrency
Go to file
MarcoFalke 79a913830e Merge #15978: .gitignore: Don't ignore depends patches
a3592c91a2 .gitignore: Don't ignore depends patches (Carl Dong)

Pull request description:

  Ignoring patches might be useful for those who use `git format-patch` often, but in our depends folder we **_want_** to keep track of our patches.

ACKs for commit a3592c:
  practicalswift:
    utACK a3592c91a2d39efe80eb5fe81511da12728d2687
  laanwj:
    utACK a3592c91a2d39efe80eb5fe81511da12728d2687
  jonasschnelli:
    utACK a3592c91a2d39efe80eb5fe81511da12728d2687
  fanquake:
    utACK a3592c9

Tree-SHA512: 439479cc2ff05335c3d21551a23b34ef2f8a4d0eb05085d2422c2c8d7d7035f529b83dc4056f18cb96234d6fa74075adaa14f0e5fb4c99e6189a4af9078fd28e
2021-02-18 14:17:24 +01:00
.github Revert "implemented labeler which automatically adds RPC label to anything modifying RPC files (#3499)" (#3517) 2020-06-11 11:44:29 +03:00
.tx Merge remote-tracking branch 'bitcoin/0.12' into HEAD 2016-02-06 16:48:04 +03:00
build-aux/m4 Merge #18298: build: Fix Qt processing of configure script for depends with DEBUG=1 2021-02-17 20:53:33 +01:00
ci Merge #13617: release: require macOS 10.10+ 2020-12-18 01:14:34 +03:00
contrib Revert "Merge bitcoin#13782: Fix osslsigncode compile issue in gitian-build" 2020-12-26 18:59:22 -06:00
depends Merge #18298: build: Fix Qt processing of configure script for depends with DEBUG=1 2021-02-17 20:53:33 +01:00
doc Merge #13717: docs: Link to python style guidelines from developer notes 2021-02-04 14:58:13 -06:00
docker build: create mountpoint for named volume (#3765) 2020-10-08 14:34:33 +03:00
share Merge #13617: release: require macOS 10.10+ 2020-12-18 01:14:34 +03:00
src chainlocks: Relay clsig inv only after bestChainLock(Hash) are assigned (#3990) 2021-02-16 16:54:19 +01:00
test instantsend: Mark blocks as conflicting when there is a CL vs IS conflict (#3987) 2021-02-14 16:09:21 -06:00
.gitattributes
.gitignore Merge #15978: .gitignore: Don't ignore depends patches 2021-02-18 14:17:24 +01:00
.gitlab-ci.yml Merge #13617: release: require macOS 10.10+ 2020-12-18 01:14:34 +03:00
.travis.yml Stage specific Travis job names (#3651) 2020-08-06 12:07:38 +03:00
autogen.sh Merge #13454: Make sure LC_ALL=C is set in all shell scripts 2020-07-28 21:35:31 -05:00
CMakeLists.txt Merge #13617: release: require macOS 10.10+ 2020-12-18 01:14:34 +03:00
configure.ac Merge #19689: build: Add Qt version checking 2021-02-17 19:25:55 +01:00
CONTRIBUTING.md Merge #13488: Docs: Improve readability of "Squashing commits" 2020-07-07 11:51:06 -05:00
COPYING Bump copyright year to 2020 (#3290) 2020-01-17 15:42:55 +01:00
INSTALL.md Dashify INSTALL.md and build-unix.md 2018-01-12 16:12:54 +01:00
libdashconsensus.pc.in Merge #7192: Unify product name to as few places as possible 2017-12-11 08:30:26 +01:00
Makefile.am qt: More asset cleanup (#3735) 2020-09-30 16:08:11 +03:00
README.md Use build badges provided by Gitlab (#3915) 2021-01-08 13:33:50 -06:00

Dash Core staging tree 0.17

CI master develop
Gitlab Build Status Build Status

https://www.dash.org

What is Dash?

Dash is an experimental digital currency that enables instant, private payments to anyone, anywhere in the world. Dash uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Dash Core is the name of the open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Dash Core software, see https://www.dash.org/get-dash/.

License

Dash Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The master branch is meant to be stable. Development is normally done in separate branches. Tags are created to indicate new official, stable release versions of Dash Core.

The contribution workflow is described in CONTRIBUTING.md.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py

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.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.

Translations

Changes to translations as well as new translations can be submitted to Dash Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Translators should also follow the forum.