Milestone Submission & Demonstration

Your milestones are marked based on your submissions to give via cs9242 git_submit. Take the time to understand these instructions to ensure that what you submit is what you want assessed.

1. Commit and push everything you wish assessed
2. Submitting for a milestone
   1. Repositories
   2. Submitting the final documentation
3. Demonstrating a milestone

Commit and push everything you wish assessed

Before generating a diff and submitting, you should ensure you have committed all files that you wish to be part of your submission. Ensure that a git status does not show untracked files that you have added or modified that should be part of your submission.

Additionally you should ensure any CMake configuration variables you have added or changed have default settings in the CMakeLists.txt. To test this, create a fresh build directory and check that the project compiles and runs as expected without invoking cmake. An example of how to do this follows:

    mkdir submission-test-build
    cd submission-test-build
    ../init-build.sh
    ninja

Submitting for a milestone

Repositories

Note that there are different submission procedures for milestone 0 and the other milestones 1 to 7:

• For milestone 0, you work in a clone of the template directory as explained int the milestone 0 description:

  https://gitlab.cs.hs-rm.de/advanced-operating-systems/aos-2020.git
  

  As you only have reporter access to that template, you can not push anything. Therefore make a git diff listing of your changes to the template and send that to me.

• For milestones 1 to 7 you work in a repository which specific to your group.

  https://gitlab.cs.hs-rm.de/advanced-operating-systems/2020_aos/{your-git-login-name}-m0
  

  Initially, this repository is created as a fork from the template. All group members have developer access, thus, they can create devlopment branches and push their modifications to the master branch when ready (assuming agreement among the group members). You must then make sure you have pushed your code to the repository on gitlab. When you submit, the latest code from the master branch should be tagged appropriately, e.g.:

      git checkout master
      git tag -a v3.0 -m "Submission Milestone 3"
  

Submitting the final documentation

The final documentation must be submitted separately by mail.

Demonstrating a milestone

When demonstrating a milestone you will need to check out the exact version of the code that you submitted.