db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Trivial Update of "ModuleVersioningPolicyReview" by DavidVanCouvering
Date Thu, 22 Sep 2005 04:50:12 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by DavidVanCouvering:
http://wiki.apache.org/db-derby/ModuleVersioningPolicyReview

New page:
This page has been created to help track comments on the ModuleVersioningPolicy.  This is
a distributed review process that has worked very well for me with previous and current distributed
teams, and I thought we could try it here.

Each reviewer creates a new row in the table for each comment.  

   * The Id column contains a unique identifier for the comment using your initials and a
number, e.g. DVC1, DVC2, etc.  
   * The Ref column contains a reference to what you are commenting on (e.g. "Section 2")
   * The Comment column is your comment
   * The Status column is used to track whether the comment is still open or closed
   * The Discussion column allows for a back-and-forth discussion.  Each comment in this column
is a new paragraph and is prefixed by the initials of the person adding to the discussion

Item EXMPL1 is an example of what this looks like.

The value of this is that each comment is tracked separately and can be resolved separately,
without a huge long email thread where concerns and issues easily gets lost and everyone gets
overwhelmed by email.

||'''Id'''||'''Ref'''||'''Comment'''||'''Status'''||'''Discussion'''||
||EXMPL1||Introduction||Are you sure we want to ref Jakarta Commons?||Unresolved||DVC: I think
it's great to use something that's already there BDF: But are they really covering the same
ground? JB: I think this is very similar||

Mime
View raw message