| 1 | [[BackLinksMenu]] |
| 2 | |
| 3 | [[TicketQuery(summary=SCS_REPO_MAINTENANCE_R3, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]] |
| 4 | = Analysis = |
| 5 | == Overview == |
| 6 | The repo maintenance should solve repository issues and create branches or tags when needed. |
| 7 | == Task requirements == |
| 8 | * Discuss |
| 9 | == Task result == |
| 10 | ^(The Analysis should contain strict requirements about the end product of the task (for example the result must be source code, the result must be google doc, etc.))^ |
| 11 | |
| 12 | == Implementation idea == |
| 13 | ^(It is advisable to include some rough implementations ideas.)^ |
| 14 | |
| 15 | == Related == |
| 16 | ^(Here you can add related tasks that could be useful or helpful.)^ |
| 17 | |
| 18 | == How to demo == |
| 19 | ^(In this section you must add instructions for the demo of the task.)^ |
| 20 | |
| 21 | = Design = |
| 22 | |
| 23 | = Implementation = |
| 24 | ^(Implementation results should be described and linked here (from the wiki or the repository))^ |
| 25 | |
| 26 | = Testing = |
| 27 | |
| 28 | = Comments = |
| 29 | ^(Write comments for this or later revisions here.) |