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

tP week 8: mid-v1.0

Lookout for these mistakes which were the most common in previous runs of the module:

Not following the required phrasing style for the first sentence of Java method header comments.
Not following the convention for Git commit message subject.
Caution: This is near-impossible to rectify later, after PR containing the commits have been merged.
Reason: While Git allows editing past commits, it changes their timestamp, which affects your weekly code contribution stats (which are factored into evaluating the consistency of your coding work over the project duration)

If you haven't done so already, make sure you know individual and team expectations of the tP

You may code from any of the below to be used in your tP, provided you give credit to the source (and do not claim such code as yours).

The iP code of any of your team members, or of any other person in the module.
Code from AddressBook-Level2 or any code used in module activities e.g., personbook

Start implementing v1.0, by adding code in small steps, while working in parallel, aiming to produce a VERY simple working version after one week, and a bit more functional version at the end of iteration (i.e., after two weeks).
See the panel below for our recommendations on the project workflow.

We recommend using the GitHub issue tracker and its milestones feature to manage your project milestones, as explained in the following panels.