Generic Infrastructure Release Process

We aim to improve the generic infrastructure release process and make it more formal:

  • Include regular promotion to master for the UI, Controller, and Contracts repositories as part of the process.

  • Share release notes at the end of the sprint. The notes should indicate which versions of UI, Controller, and Contracts work well together.

  • The nightly build of the dummy code processor should validate the integration of the current versions of Controller and UI in master.

Work items:

  • Use GitFlow only on UI, Controller, and Contracts. Other repositories like utils, assessment model, and licensing should GitHubFlow in order to reduce unnecessary overhead in the release process.

  • Work with Carlos to configure the nightly build of the dummy code processor.

  • Move Electron CGI adapter to UI repo.

Last updated