Feedback on week 10 project progress

nus-se-bot commented 5 years ago

Subject: feedback on week 10 project progress

See mid-v1.3 progress guide for more details of the activities mentioned below.

Team progress

Recommended progress for v1.3

Milestone v1.3 managed systematically
- [x] A suitable deadline set (:heavy_check_mark: well done!)
- [x] Issues allocated to it e.g., link (:heavy_check_mark: well done!)
[x] A new jar file has been released on GitHub (:heavy_check_mark: well done!)

Individual progress of @andrewtanjs

Recommended progress for v1.3

[x] Has issues/PRs assigned for the milestone (:heavy_check_mark: well done!)

Individual progress of @cyrusguo

Leftovers from v1.2

[ ] Merged updates to the Developer Guide (:exclamation: try to do by next milestone)

Recommended progress for v1.3

[ ] Has issues/PRs assigned for the milestone (:exclamation: try to do by next milestone)

Individual progress of @preethi-d

Recommended progress for v1.3

[x] Has issues/PRs assigned for the milestone (:heavy_check_mark: well done!)

Individual progress of @alyip98

Leftovers from v1.2

[ ] Merged updates to the Developer Guide (:exclamation: try to do by next milestone)

Recommended progress for v1.3

[x] Has issues/PRs assigned for the milestone (:heavy_check_mark: well done!)

Individual progress of @yogtew

Leftovers from v1.2

[ ] Merged updates to the Developer Guide (:exclamation: try to do by next milestone)

Recommended progress for v1.3

[ ] Has issues/PRs assigned for the milestone (:exclamation: try to do by next milestone)

Tutor: @parvathy-sudhir-pillai

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2018-10-24 00: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.

yogtew commented 5 years ago

Hi, I have issues assigned for the next milestone i.e v1.3. Attached is the screenshot! Thank you!

Yogusvi Tewari

On Wed, Oct 24, 2018 at 8:26 AM cs2103-feedback-bot < notifications@github.com> wrote:

Subject: feedback on week 10 project progress

See mid-v1.3 progress guide https://nus-cs2103-ay1819s1.github.io/cs2103-website/admin/project-w10-mid-v13.html for more details of the activities mentioned below. Team progress Recommended progress for v1.3

Milestone v1.3 managed systematically

A suitable deadline set (✔️ well done!)

Issues allocated to it e.g., link https://github.com/CS2103-AY1819S1-W13-3/main/issues/18 (✔️ well done!)

A new jar file has been released on GitHub (✔️ well done!)

Individual progress of @andrewtanJS https://github.com/andrewtanJS Recommended progress for v1.3

Has issues/PRs assigned for the milestone (✔️ well done!)

Individual progress of @cyrusguo https://github.com/cyrusguo Leftovers from v1.2

Merged updates to the Developer Guide (❗️ try to do by next milestone)

Recommended progress for v1.3

Has issues/PRs assigned for the milestone (❗️ try to do by next milestone)

Individual progress of @preethi-d https://github.com/preethi-d Recommended progress for v1.3

Has issues/PRs assigned for the milestone (✔️ well done!)

Individual progress of @alyip98 https://github.com/alyip98 Leftovers from v1.2

Merged updates to the Developer Guide (❗️ try to do by next milestone)

Recommended progress for v1.3

Has issues/PRs assigned for the milestone (✔️ well done!)

Individual progress of @yogtew https://github.com/yogtew Leftovers from v1.2

Merged updates to the Developer Guide (❗️ try to do by next milestone)

Recommended progress for v1.3

Has issues/PRs assigned for the milestone (❗️ try to do by next milestone)

Tutor: @parvathy-sudhir-pillai https://github.com/parvathy-sudhir-pillai

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2018-10-24 00: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.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/CS2103-AY1819S1-W13-3/main/issues/55, or mute the thread https://github.com/notifications/unsubscribe-auth/AfDZN-3BvirsXVtq1RwDE40Cs5Me-U7Hks5un7O-gaJpZM4X254t .

damithc commented 5 years ago

I have issues assigned for the next milestone i.e v1.3. Attached is the screenshot!

To be clear, there should be issues in milestone v1.3 that have been assigned to you. I checked the milestone just now and none seem to be assigned to you?

yogtew commented 5 years ago

Hello Prof,

I didn’t know that after creating the issues, we need to assign them to ourselves. I just created the issue and assigned it to the milestone. So just to clarify, we need to assign issues to ourselves or others after creating them? Just creating the issue is not counted?

Thank you, Regards Yogusvi

On Wed, 24 Oct 2018 at 1:22 PM, Damith C. Rajapakse < notifications@github.com> wrote:

I have issues assigned for the next milestone i.e v1.3. Attached is the screenshot!

To be clear, there should be issues in milestone v1.3 that have been assigned to you. I checked the milestone just now and none seem to be assigned to you? [image: image] https://user-images.githubusercontent.com/1673303/47407917-d1813080-d78f-11e8-8469-70dbf9201369.png

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/CS2103-AY1819S1-W13-3/main/issues/55#issuecomment-432516828, or mute the thread https://github.com/notifications/unsubscribe-auth/AfDZN3D3qmRJNbblUY2UTRCQ5Hon3PGqks5un_kogaJpZM4X254t .

damithc commented 5 years ago

I didn’t know that after creating the issues, we need to assign them to ourselves.

The issue author is not necessarily the person who is tasked to submit a fix for the issue. So yes, you need to indicate who is being assigned to submit a fix for the issue. We use the assignee field for that.

CS2103-AY1819S1-W13-3 / main