High-level principles related to the development of the system
- software assets to be held on GitHub
- software to be licensed under the Apache 2 license
- code repositories will use the GitFlow branching model
- contributors make changes by submitting Pull Requests
- editors review pull requests for consistency prior to merging into
develop
- periodically, editors create a
release
candidate (where appropriate, editors will seek wider review of release candidate assets including clinical review, Connectathon testing etc) - following successful review, assets are marked as active and published to
master
branch.
- software assets will follow Semantic Versioning
- major versions will be maintained in parallel for a period of time before deprecation
- Github Webhooks will be used to automatically build & publish software assets to a public test instance