Changes between Version 2 and Version 3 of SCHEDULE_MAINTENANCE_R3

Timestamp:

05/08/09 09:33:54 (16 years ago)

Author:

deyan

Comment:

--

SCHEDULE_MAINTENANCE_R3

@@ -9 +9 @@
 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.)^
-
+ * Create a list with the existing stickies
+ * Create a list with suggestions for new stickies
+ * Order the list by priority (you decide which group of functionality has highest priority
+ * Research in what phase we are on each functionality (none, proto, base)
+ * Decide if the list should be split in sections 
 == Task result ==
-^(List the end product of the task (for example "Source code", "Wiki page", etc.))^
+[wiki:SCHEDULE_MAINTENANCE]
 
 == Implementation idea ==
-^(Provide some rough implementation idea(s).)^
-
+For each list item you may explain what is needed, your comments, etc. You may use bullets for better reading
 == Related ==
 ^(Add links to related tasks that could be useful or helpful.)^
 
 == How to demo ==
-^(Provide instructions for demonstration of the task.)^
+Show the list and explain some list items.
 
 = Design =