Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback on week 8 project progress #24

Open
16 of 22 tasks
nus-pe-script opened this issue Oct 9, 2018 · 2 comments
Open
16 of 22 tasks

Feedback on week 8 project progress #24

nus-pe-script opened this issue Oct 9, 2018 · 2 comments

Comments

@nus-pe-script
Copy link

nus-pe-script commented Oct 9, 2018

Subject: feedback on week 8 project progress

See v1.1 progress guide for more details of the activities mentioned below.
Mid-milestone progress reports are FYI only. They are not graded.

Team progress

Recommended progress for the upcoming milestone

  • Issue labels set up e.g., type.*, priority.* (:exclamation: try to do by next milestone)
  • Milestones created: v1.2 v1.3 v1.4 [Please ensure milestones are setup until 'v1.4'] (:heavy_check_mark: well done!)
  • Issues marked as type.Story e.g., link (:heavy_check_mark: well done!)
  • Some issues prioritized using priority.* labels e.g., link (:heavy_check_mark: well done!)
  • Milestone v1.2 planned
  • A suitable deadline set (:heavy_check_mark: well done!)
  • Issues allocated to v1.2 e.g., link (:heavy_check_mark: well done!)
  • Issues allocated to v1.3 e.g., link (:heavy_check_mark: well done!)
  • Build passing (:heavy_check_mark: well done!)

Individual progress of @shuanang

Leftovers from v1.1

  • Used forking workflow:
    • Forked team repo (:heavy_check_mark: well done!)
    • Created PRs (:exclamation: try to do by next milestone)
    • Gave review comments to other PRs (:exclamation: try to do by next milestone)

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:exclamation: try to do by next milestone)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @arjo129

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @cjunxiang

Leftovers from v1.1

  • Used forking workflow:
    • Forked team repo (:heavy_check_mark: well done!)
    • Created PRs link (:heavy_check_mark: well done!)
    • Gave review comments to other PRs (:exclamation: try to do by next milestone)

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @TTTaus

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:exclamation: try to do by next milestone)
  • Has issues/PRs assigned for the next milestone (:exclamation: try to do by next milestone)

Tutor: @okkhoy

Note: the above observation was done by the CS2113-feedback-bot and covers changes up to 2018-10-10 02:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

@arjo129
Copy link

arjo129 commented Oct 10, 2018

The labels for the issue tracker were already set up.

@okkhoy
Copy link

okkhoy commented Oct 11, 2018

@arjo129 yes. we have checked and updated the records.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants