This site is from a past semester! The current version will be here when the new semester starts.

Week 3 [Fri, Aug 20th] - Project

iP:

  1. Do any leftover iP tasks from the previous week
  2. Create a PR to the upstream repo by the end of the lecture
  3. Add Increments: Level-4, A-TextUiTesting, A-CodingStandard

tP:

  1. Set up a project meeting time by the end of the lecture

iP

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 Create a PR to the upstream repo by the end of the lecture

  • Create a pull request (PR) from your fork to the upstream repo. Note the following:
    • Create the PR from the master branch of your fork to the master branch of the upstream repo (https://github.com/nus-tic4001-AY2122S1/ip)
    • Set the PR name as [{Your name}] iP e.g., [John Doe] iP If you are reluctant to give full name, you may give the first half of your name only.
      You may leave the description as empty.
    • If you created the PR correctly, it should appear in the list of PRs here.
    • Steps for creating a PR is given in this textbook topic (steps 5 onwards):

The PR will update automatically to reflect your latest code every time you push code to your fork. As a result, it provides a convenient way for us to access the current state of all your iP code from one location.

3 Add Increments: Level-4, A-TextUiTesting, A-CodingStandard

Duke Level-4: ToDo, Event, Deadline
Duke A-TextUiTesting: Automated Text UI Testing optional
Duke A-CodingStandard: Follow the Coding Standard

tP: Kickoff

1 Set up a project meeting time by the end of the lecture

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