Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
E
E-CAM-Library
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 60
    • Merge Requests 60
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • e-cam
  • E-CAM-Library
  • Merge Requests
  • !262

Merged
Opened Sep 28, 2020 by Georgia Christopoulou@gechri8Contributor11 of 13 tasks completed11/13 tasks

Module: Direct Dynamics Database

  • Overview 15
  • Commits 18
  • Pipelines 12
  • Changes 3

Add a brief description briefly here (which replaces this sentence), a line or two is usually enough.

Module verification checklist (for reviewers)

Checklist when the module is first submitted

  • Have the relevant labels been added to the MR
  • If submitted on someone elses behalf, has the software author been referenced (if they have a GitLab account)

Checklist when module is no longer "WIP"

  • Is the module documentation sufficiently detailed?
  • Is it mergeable? (i.e., there should be no merge conflicts)
  • Are the build instructions sufficient - source code locations, build instructions, etc.? (If not the MR should be updated)
  • Did it pass the tests that were described? (Are there unit/regression tests? Do they pass?)
  • Are the tests sufficient?
  • If the module introduces new functionality, is it tested? (Unit/regression tests?)
  • Is the associated source code well formatted? (typos, line length, brackets,...it should be consistent with existing source)
  • Is all new source code sufficiently documented? (functions, their arguments,...)
  • Is there a description of any applications the module has? (This is a hard requirement for E-CAM PDRAs)

After Merging

  • Make sure the module appears in a toctree
  • Add a link to the final result on https://e-cam.readthedocs.io
Edited Oct 21, 2020 by Jony Castagna
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: e-cam/E-CAM-Library!262
Source branch: master

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.