iP:
Level-7
, Level-8
A-MoreOOP
, A-Packages
, A-Gradle
, A-JUnit
, A-Jar
A-JavaDoc
, A-CodingStandard
, Level-9
tP:
You are required to follow the Git standard from this week, as specified in this page.
Only future commits need to follow the Git standard. Editing past commit messages (to make them comply with the Git standard) is discouraged as it changes the commit timestamp, which can alter your iP progress timeline (as seen by progress tracking scripts).
Reminder about the deadline for the weekly project tasks:
master
branch of your fork to the master
branch of the upstream repo (https://github.com/nus-cs2103-AY2324S2/ip)[{Your full/partial name or your Github username}] iP
[Richard Mathews Chee] iP
or [Rich ... hee] iP
or [TheRichMat] iP
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.
Level-7
, Level-8
branch-Level-7
. Here are the steps:
branch-Level-7
.master
branch as usual (i.e., add the tag Level-7
).master
branch, push the branch-Level-7
, and push the tag, to your fork.b1
to the master
branch, you need to push both the master
and the b1
branches to the fork. Pushing the master
branch does not automatically take the b1
branch along with it just because it is already merged to the master
branch.branch-Level-8
.A-MoreOOP
, A-Packages
, A-Gradle
, A-JUnit
, A-Jar
master
branch will always stay in a 'unbroken' state as the work-in-progress will be in a separate branch till such work is ready to be merged.A-Gradle
you can use the Gradle option (rather than the IntelliJ option) when doing A-JUnit
and A-JAR
as they are easier to do using Gradle.Note that if A-Jar
increment does not require any code changes, you may tag the commit at which this was achieved as A-Jar
(even if that commit has another tag already). Otherwise, tag the latest commit as usual. In both cases, push the tag to the fork.
A-JavaDoc
, A-CodingStandard
, Level-9
branch-A-JavaDoc
, branch-A-CodingStandard
, branch-Level-9
), and then merge them one-by-one. Hopefully, you will encounter some merge conflicts so that you get to practice de-conflicting branches.A-CodingStandard
) are given in this page.If you can spare some time, start learning JavaFX by following the JavaFX tutorial @SE-EDU/guides. Doing so will make your life easier in the following week.
indicates an individual task (i.e., each team member has to do the task, graded individually)
indicates a team task (some or all members may do the work; graded for the whole team).
Objectives: (1) To get each of you to think of ways to improve AB3 (2) To detect any Java version compatibility issues between your local set up and the expected Java version.
Submission: via Canvas survey named tP: AB3 Initial Experience
by Sat, Feb 3rd 23:59
Steps:
add ...
command)..png
file.One member is slightly behind and one significantly behind. We plan to have a code-together session on Sunday so that we can help them if they encounter problems.