tP Week 12: v2.1

Deadline for all v2.1 submissions is Tue, Nov 3rd 14:00:00 unless stated otherwise. Note that 14:00:01 is considered late, as per the Canvas deadline mechanism.

Penalty for late submission (per file):
-1 mark for missing the deadline (up to 2 hours late).
-2 for an extended delay (up to 24 hours late).
Penalty for delays beyond 24 hours is determined on a case-by-case basis.

• Even a one-second delay is considered late, irrespective of the reason.
• For submissions done via Canvas, the submission time is the timestamp shown by Canvas.
• When determining the late submission penalty, we take the latest submission even if the exact same file was submitted earlier. Do not submit the same file multiple times if you want to avoid unnecessary late submission penalties.
• The whole team is penalized for problems in team submissions e.g., a -1 penalty for a team submission will be a -1 penalty for each team member.
  Only the respective student is penalized for problems in individual submissions.

Submit via the Canvas assignment we have set up.

Follow submission instructions closely. Any non-compliance will be penalized (e.g., wrong file name/format).
Canvas might automatically add a file name suffix (e.g., *-1.jar, *-2.jar, ...) if you upload a file multiple times. You can safely ignore that suffix.

Do not update the code during the 30 days after the deadline. Get our permission first if you need to update the code in the repo during that code-freeze period.

• You can update issues/milestones/PRs even during the code-freeze period.
• You can update the code during the code-freeze period if the change is related to a late submission approved by us.
• You can continue to evolve your repo after the code-freeze period.