Development Work Flow and Code Reviews Sample Clauses

Development Work Flow and Code Reviews. ‌ In order to ensure high software quality and ease of software deployment (also to max- imise dissemination and uptake of ILIAD’s outcomes), the Continuous Integration and deployment paradigm is facilitated through a build farm infrastructure that is committed to ILIAD by UoL (see above). Within the project, we have agreed to use a git-based workflow, collaborating on software repositories stored publicly at ▇▇▇▇://▇▇▇▇▇▇.▇▇▇/ or other public git-based repositories, when possible, or at partner-local repository servers, when required to maintain intellectual property rights. The general workflow follows the “fork and pull” model [1], which is well integrated with continuous integration. The general workflow is captured in Figure 4. ▇▇▇▇▇ has designated named maintainers for individual software packages, who are responsible for code review and assessment of pull/merge requests. They are supported by the CI server, which will compile and unit-test any opened requests to facilitate the assessment prior to any merges to the master code base. Releases are only ever tagged on the master branch 2▇▇▇▇▇://▇▇▇▇▇▇▇.▇▇/ Core Team Contributor create fork «cre spect comme optional as a result of inspection m ar c lose commits e pulled erge ment commit nt commit ate» in Figure 4: Overview of the fork and pull model used for code review and integration work flow in ILIAD (taken from [1]). and undergo a dedicated review process by the technical board before accepted into the ILIAD distribution.