| CI | master | develop |
|---|
Introduction The rapid global development demands a comprehensive transformation. Arsagility transforms by offering sustainable products and services, adapting to today's market needs. With the Go Beyond Next spirit that demonstrates creativity we will act differently and always go beyond the reach in innovation. Our actions always prioritize the needs of the global community and planet earth. Our focus is to build production and distribution ecosystems that are environmentally friendly, build the capabilities of workers and communities, present digital solutions, and ensure a positive impact for the future.
Arsagility Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.
The master branch is meant to be stable. Development is done in separate branches.
Tags are created to indicate new official,
stable release versions of Arsagility Core.
The contribution workflow is described in CONTRIBUTING.md.
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.
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.
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.