On Thursday 30 June 2011 08:19 PM, C. Michael Pilato wrote:
On 06/30/2011 04:58 AM, ar...@apache.org wrote:
Author: arwin
Date: Thu Jun 30 08:58:11 2011
New Revision: 1141447
URL: http://svn.apache.org/viewvc?rev=1141447&view=rev
Log:
Added branch milestones document.
* BRANCH-MILESTONES : New file.
Why a second branch-specific file? Put this information into the
"BRANCH-README" file where folks will know to look for it.
That sounds better Mike. Attaching a patch to put the "milestones" information into the
"branch-readme" file.
Also attached is the log message.
Since I am working on this branch, I checked out the branch and started working
on it. Hence this patch is with
respect to the *svn-bisect* branch.
Thanks and regards
Prabhu
Index: BRANCH-README
===================================================================
--- BRANCH-README (revision 1141838)
+++ BRANCH-README (working copy)
@@ -68,3 +68,43 @@
The above mentioned exit codes conform to the way git bisect does
things.
+
+
+
+MILESTONES
+==========
+This part of the document serves as a progress tracker by defining
+the milestones that need to be completed. It contains a set of phases,
+each with it's own tasks.
+
+
+PHASE 1
+-------
+
+Task Status
+
+1.1 Write skeleton code with bare minimum [Not Started]
+ implementation. This involves creating
+ the new source files in the various
+ modules and the skeleton API.
+
+1.2 Define a set of unit tests to clearly [Started]
+ define the expected behaviour. This
+ will be an on-going task and will not
+ be a phase blocker.
+
+1.3 Implement the tests. [Not Started]
+
+
+PHASE 2
+-------
+
+Task Status
+
+2.1 Implement the behaviour as defined by [Not Started]
+ the test suite.
+
+2.2 Check for consistency of code, error [Not Started]
+ handling and error codes.
+
+
Index: BRANCH-MILESTONES
===================================================================
--- BRANCH-MILESTONES (revision 1141838)
+++ BRANCH-MILESTONES (working copy)
@@ -1,34 +0,0 @@
-This document serves as a progress tracker by defining the milestones
-that need to be completed. It contains a set of phases, each with
-it's own tasks.
-
-
-PHASE 1
-=======
-
-Task Status
-
-1.1 Write skeleton code with bare minimum [Not Started]
- implementation. This involves creating
- the new source files in the various
- modules and the skeleton API.
-
-1.2 Define a set of unit tests to clearly [Started]
- define the expected behaviour. This
- will be an on-going task and will not
- be a phase blocker.
-
-1.3 Implement the tests. [Not Started]
-
-
-PHASE 2
-=======
-
-Task Status
-
-2.1 Implement the behaviour as defined by [Not Started]
- the test suite.
-
-2.2 Check for consistency of code, error [Not Started]
- handling and error codes.
-
No need of a separate Branch-Milestone file
* BRANCH-README
Added the milestones for this branch.
* BRANCH-MILESTONES
Deleted the file and moved the contents to BRANCH-README file
Patch by: Prabhu Gnana Sundar <prabhugs{_AT_}collab.net>
