wiki:SCHEDULE_MAINTENANCE_R3

Version 2 (modified by deyan, 16 years ago) (diff)

--

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

Error: Macro TicketQuery(summary=SCHEDULE_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|) failed
current transaction is aborted, commands ignored until end of transaction block

Analysis

(Give as much as possible of the needed information for designing and implementing the task in the following sections.)

Overview

It turned out to be a good idea to collect functionalities on sticky notes and prioritize by these notes. In order to make a good priority of the things, we should create a wiki page with these functionalities and subfunctionalities and prioritize them someway. After discussion with the team, these should be considered as priority list and people should choose tasks from these groups.

Task requirements

(List the necessary requirements that the task must fulfill.)

Task result

(List the end product of the task (for example "Source code", "Wiki page", etc.))

Implementation idea

(Provide some rough implementation idea(s).)

(Add links to related tasks that could be useful or helpful.)

How to demo

(Provide instructions for demonstration of the task.)

Design

(Describe your design here.)

Implementation

(Describe and link the implementation results here (from the wiki or the repository).)

Testing

(Place the testing results here.)

Comments

(Write comments for this or later revisions here.)