Integration & Delivery
1. Treatment
Once a bug is reported, a feature is requested or a payoff is needed, we add a new ticket to our backlog tagged with the corresponding flag (bug, feature, payoff, project) and priority level.
3. Non-Regression Tests
In order to ensure that the updated code is not impacted by any subsequent modifications, at the end of each developpement session, a new non-regression test is submitted to our test basis.
2. Developpement
A branch is then created from the master branch of our codebase, located on a private GitHub repository which access is restricted to our developpers only.
4. Integration
A pull request is submitted and triggers our custom GitHub actions to execute builds and tests on our cross-platform self-hosted runners. The branch is merged if only all builds and tests passed on all tested configurations.
5. Delivery
Every business day, if at least one merge has not been released yet, a shell script writes a changelog and pushes a tag that follows semantic versioning principles. This push triggers a packaging for each configurations supported.
6. Follow up
For any requests, an estimated time of arrival (ETA) is communicated and in the meantime some meetings can be organized for you to follow up the progression of the project.
