Comment
Author: Admin | 2025-04-28
Litecoin Core integration/staging treehttps://litecoin.orgWhat is Litecoin?Litecoin is an experimental digital currency that enables instant payments toanyone, anywhere in the world. Litecoin uses peer-to-peer technology to operatewith no central authority: managing transactions and issuing money are carriedout collectively by the network. Litecoin Core is the name of open sourcesoftware which enables the use of this currency.For more information, as well as an immediately useable, binary version ofthe Litecoin Core software, see https://litecoin.org.LicenseLitecoin Core is released under the terms of the MIT license. See COPYING for moreinformation or see https://opensource.org/licenses/MIT.Development ProcessThe master branch is regularly built and tested, but is not guaranteed to becompletely stable. Tags are createdregularly to indicate new official, stable release versions of Litecoin Core.The contribution workflow is described in CONTRIBUTING.md.The developer mailing listshould be used to discuss complicated or controversial changes before workingon a patch set.Developer IRC can be found on Freenode at #litecoin-dev.TestingTesting and code review is the bottleneck for development; we get more pullrequests than we can review and test on short notice. Please be patient and help out by testingother people's pull requests, and remember this is a security-critical project where any mistake might cost peoplelots of money.Automated TestingDevelopers are strongly encouraged to write unit tests for new code, and tosubmit 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 runningand extending unit tests can be found in /src/test/README.md.There are also regression and integration tests, writtenin 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.pyThe 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) TestingChanges should be tested by somebody other than the developer who wrote thecode. This is especially important for large or high-risk changes. It is usefulto add a test plan to the pull request description if testing the changes isnot straightforward.TranslationsWe only accept translation fixes that are submitted through Bitcoin Core's Transifex page.Translations are converted to Litecoin
Add Comment