search

nus-cs2103-AY2021S1 / forum

20 stars 2 forks source link

1.3 milestone un-done #376

Closed zhiayang closed 4 years ago

zhiayang commented 4 years ago

So I re-opened an issue assigned to 1.3 (realised it wasn't fully fixed), without re-assigning it to the 1.4 milestone, and looks like the progress-checking-script caught the repo with the issue open, so now my team's 1.3 wrap up is currently marked as un-done.

I already re-assigned the issue to 1.4, but hopefully there won't be a penalty for this?

damithc commented 4 years ago

I already re-assigned the issue to 1.4, but hopefully there won't be a penalty for this?

It will turn green at the next update. No penalty. The purpose of the dashboard is to help you self-detect and self-correct this kind of things. We don't penalize unless the compliance rate is very low (OK to miss a few here and there) and there is no attempt to self-correct.

zhiayang commented 4 years ago

ok, thanks prof!