Week 3 [Mon, Jan 26th] - Project

iP:

  1. Do any leftover iP tasks from the previous week
  2. Add Increments (+ commit, tag, push): Level-1, Level-2, Level-3, A-CodingStandard

tP:

  1. Team Task: Set up a project meeting time by the end of the tutorial

iP

Reminder about the deadline for the weekly project tasks:

1 Do any leftover iP tasks from the previous week

  • Remember to do any leftover increments from the past weeks before starting on the current week's increments. This guideline applies to future weeks too.

2 Add Increments (+ commit, tag, push): Level-1, Level-2, Level-3, A-CodingStandard

  • From this point onward, after completing each increment,
    • git tag the commit that completed the increment with the exact increment ID e.g., Level-2, A-TextUiTesting
      Git tags are not the same as Git commit messages.
      %%{init: { 'theme': 'default', 'gitGraph': {'mainBranchName': 'master'}} }%%
gitGraph
  commit id: "..."
  commit id: "Rename main class"
  commit id: "Add greeting" tag: "Level-0"
  commit id: "Add support for echo"
  commit id: "Fix bug in echo" tag: "Level-1"
  commit id: "Add support for list"
  commit id: "Add support for bye"
    • git push the code to your fork
      Git doesn't push tags unless you specifically ask it to. After pushing a tag to your fork, you should be able to see that tag by visiting https://github.com/YOUR_USER_NAME/REPO_NAME/tags e.g., https://github.com/se-edu/addressbook-level3/tags
      If you encounter issues connecting Sourcetree with your GitHub account, refer to this Sourcetree Tutorial.
  • The relevant textbook topics are:
Duke Level-1: Echo
Duke Level-2: Add, List
Duke Level-3: Mark as Done
Duke A-CodingStandard: Follow the Coding Standard

FAQ What to do if a certain aspect is not covered by the Java/Git standard?

tP: Kickoff

Intro to tP Week 3

1 Team Task: Set up a project meeting time by the end of the tutorial

  • After forming teams, set up a weekly project meeting time/venue (and communication channels) with your team members:

  • Submission (one person per team): via Canvas. Submission will open Friday evening, after team forming is complete for all tutorials. We'll let you know when it is open.
    Details to submit:
    • Which day of the week, and at what time, your team will hold weekly team meetings?
    • What is the mode (online or F2F)?
    • If F2F, where will you be meeting? If Online, which software will you be using for the meeting?
    • Have all teams explicitly agreed to the above plan? If anyone has not agreed, state who and why (e.g., uncontactable).

FAQ What if a member is not contactable?