List view
This is the second phase of the Initation Sprints. The developers have started to get an idea of how Muze works, and further with this sprint, they should have a well developed understanding of how to effectively close an issue along with developer reviews. Devs will also get a better understanding of how the Muze Development works, with more time allocated to closing issues than time spent on understanding the same. Before completing an issue, make sure: You have written test cases for the issue Branches made correspond to the issue id, For example, for issue id #74, the branch name should be "feature/#74-..." Ensure the completion of the issue
Overdue by 7 year(s)•Due by January 25, 2019This is the first sprint of 2019, where most of the developers will get an introduction to how Muze works. Before completing an issue, make sure: 1) You have written test cases for the issue 2) Branches made correspond to the issue id, For example, for issue id #74, the branch name should be "feature/#74-..." 3) Ensure the completion of the issue
Overdue by 7 year(s)•Due by January 17, 2019