At the end of each development iteration, once all team members’ tasks have been completed and their pull requests have been merged into the main branch, your team must create a GitHub release for the milestone.
| Release Field | Example Values |
|---|---|
| Tag version | m1, m2 |
| Release title | Milestone M1, Milestone M2 |
The following are three key criteria for your team’s code submission:
Code builds and runs. I should be able to build and run the code in the project’s main branch using the usual approach covered in the course. If any special instructions are required to build/run your software, include them in the project’s README file.
Code quality. Your code must follow common style guidelines and be well organized and readable. For example, all code must be properly indented, and class/variable/method names must be sensible. You should also do your utmost to avoid bugs and other sloppiness.
Replicable demo. I should be able to replicate your demo video. If certain data is required to do so, you must somehow make that data available to me. Also, I suggest putting instructions for how to replicate the demo in the project’s README file.
Each milestone release will be graded pass (full points) or fail (0 points) based on whether or not the GitHub release was created correctly.