okkhoy
commented
2 years ago Thanks @wilsonngja for asking here again. I hope the question and responses help the rest of the class.
I suggest each of you do the part of updating the issue tracker and managing it as and when the items are cleared.
the one that will be creating these would be the one that is allocated to this task right
If you follow the above suggestion, yes. You create relevant issues (user story, task, bug**) before you work on something. Assign the issue to yourself, set the milestone and labels appropriately Fix the issue (using Fixes #\<num>) when PR is created. So on merging the PR, the issue is automatically closed.
** if it is a bug in a different part of the codebase, you are still encouraged to record it and assign the concerned team member.
if my role is to maintain the workflow, while my teammate's role is to maintain the documentation, then I would be the one assigning the issues, and approving the PR etc right
- I suggest at least 2 people manage the PR approving process. If the "approver" falls sick/gets busy/goes MIA, then there is a backup to ensure the project is not stalled.
- Alternatively, you can do round-robin or take some turns to approve one another's PR
- Also, shared load is better for all involved
- Additionally, please ensure someone else looks at the code and then approves the PR, not the author themselves.
Did I answer your questions? Did I miss anything?
With regards to the creation of user stories and milestones, the one that will be creating these would be the one that is allocated to this task right? So for example if my role is to maintain the workflow, while my teammate's role is to maintain the documentation, then I would be the one assigning the issues, and approving the PR etc right?