All Collections
Reliability
Software Development Life Cycle
Software Development Life Cycle

Change, review, release, deploy

Updated over a week ago

Isolate code

A branch is created from the current master branch. The branch is name with the employees first name pre-pended: jane/some-feature

Writing code

Changes are implemented as described in the task, and employees are required to ask their superior if anything is the slightest unclear. Moreover, employees are urged to - communicate early and a lot and to think through the changes required for the change. Additionally, to reflect on what implications it might have on infrastructure/security/network/communication/design/API design etc. Moreover, employees are instructed to make sure to consult our documentation and our wiki and ask/discuss with colleagues and/or the manager if not sure.

Create a pull/merge request on SCM platform (GitHub)

Employees include the Notion task link in the PR description if applicable.

Submit for review

  • If deemed necessary employees are instructed to reach out to the person applicable to review or post a link to the PR in the appropriate team Slack channel, team-{frontend|backend}.

  • Necessary changes after that the reviewers input are implemented.

  • If any infrastructure/security/network/communication/design/API design changes have been made, employees are urged to be extra careful and make sure the relevant colleague and/or manager are informed.

Release / How to deploy

The company has clear instructions for how to deploy provided to the company’s employees in the company's wiki How to Deploy.

Did this answer your question?