Changes between Version 5 and Version 6 of ITERATION_03/Release/Process

Timestamp:

12/20/08 16:31:24 (16 years ago)

Author:

pap

Comment:

--

ITERATION_03/Release/Process

@@ -11 +11 @@
  * Bugfixing
 
-== Opening ==
+=== Opening ===
 This are the first things that the team should do after the official sprint opening:
  * Create a branch from the trunk. The name should be further determined(perhaps something like release01 or release01-pre-alpha-2)
@@ -19 +19 @@
  * Disable nonworking functinality that is not supposed to be available and is messing the other code.
 
-== Testing ==
+=== Testing ===
 This refers to the last phase of a task's revision lifecycle. 
 
@@ -40 +40 @@
  * Have a look at related bugs - this means look if there are new bugs in the related tests.
 
-== Reviews ==
+=== Reviews ===
  * We should do reviews on implementations done by functional teams
  * It this is needed we could help with desgin reviews
 
-== Release Asembly ==
+=== Release Asembly ===
  * Final bugfixes
  * Find workarounds for those bugs that cannot be fixed but
@@ -50 +50 @@
  * Make the download page
  * Make the downloadanbles
+
+=== Bugfixing ===
+
+ * Choose bugs to fix from the opened ones in Trac
+ * Take the bug ticket
+ * Research for a bugfix
+ * If a fix is available its resul must be described in the ticket
+ * Change the status of the ticket
+
+== Iteration schedule ==
+ * The iteration begins with the general sprint opening - 1d
+ * Do release team opening as described above - 2d
+ * Start testing and bugfixing.
+ * Start making reviews. We should always keep the tasks pending for a review as less as possible.
+ * As the iteration progresses the less effort is spent on testing and more on reviewing.
+ * Do the rekease assembly - 4d
+ * Do the demo and the sprint closing
+
+You can also look at the attached photos.