Skip to content

Instantly share code, notes, and snippets.

@Furao

Furao/gitlab_process.md

Created June 4, 2014 16:47
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Furao/d98d13659bdf48224581 to your computer and use it in GitHub Desktop.
Save Furao/d98d13659bdf48224581 to your computer and use it in GitHub Desktop.
Download ZIP
DO-178C gitlab process
Raw
gitlab_process.md

Use Case: I need to add some new requirements.

  • Create a new branch and add all of my requirements
  • Make a pull request to master
  • All of the new requirements are easily shown in the gitlab pull request
  • Reviewers would add their comments in gitlab to specific lines.
  • Developers would be able to comment back and forth in the comment section of the pull request and then make fixes
  • Reviewers can then verify once a fix has been made (Add a new comment to the line saying it is fixed?)
  • All changes have been accepted so the branch is merged into master

Through this process, the only requirements that will actually be in the master will be fully reviewed requirements. (Can we force gitlab to not allow writing to master, only merges?)

DER Involvement

The DER needs to review all of our certification artifacts which includes reviews. Through this process, all requirements reviews will be contained in the pull requests. Each pull request will include the following data:

  • Added/Modified requirements and their authors
  • Issues and the reviewer that added it
  • Fixes and author
  • Verification of each issue and Verifier
  • Date and Times

This data should be sufficient for the DER, provided you can't modify or delete this data after the fact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment