Finalize your Project Specification and Timeline with Milestone Descriptions

[bassoy]

Dear stipends

According to the timeline, coding should start from June 7th. Of course you can start to code earlier. However, it is very important to first specify your project and milestone using the Github Kanban board and the already created in the Wiki and that you are in sync with mentor.

Each stipend should (wiki)

• describe his/her own project in the wiki: (references are wiki18 or wiki19.
• describe why the project is needed in Boost.uBlas
• mention/describe your milestones (one milestone for each phase) that you have mentioned/described
• describe what the definition of done is for each of the milestone

Each stipend should (Kanban board)

• describe his/her own project on the Kanban board - @shikharvashistha in more detail please
• create your labels - as you already did
• include your milestones - this one requires specific names and description - put the definition of done inside
• include your initial tasks and discuss this with your mentor

[kannavkm]

I seem to have completed the above-mentioned tasks, kindly review them.
I have kept the testing(here I mean rigorous testing, I'll be doing some amount testing during the implementation phase though it might be not as concrete) and documentation as separate phases, is that fine? or would doing testing and documentation side by side be better.

[bassoy]

You can improve on some points:

1. documentation and testing should be part of each phase as issues (tasks)
2. if I navigate to the milestones, I do not see an tasks - pull your tasks into the milestone
3. please delete unused milestones
4. include what definition of done for each milestone

[kannavkm]

1. Sure I have added that within the respective milestone, I'll update the changes in the wiki also.
2. Added tasks in the respective milestones, all milestones and issues of mine start with ST tag.
3. Deleted unused milestones
4. Present in the wiki, but I'll add that to the description of milestones itself