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] Update of "SharedComponentVersioningGuidelines" by DavidVanCouvering
Date Mon, 17 Oct 2005 22:02:22 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/SharedComponentVersioningGuidelines

------------------------------------------------------------------------------
  
  == Documenting Shared Components ==
  
- We will provide a top-level {{{README}}} file under {{{java/org/apache/derby/common}}} that
describes the shared components guidelines (once they are approved) and lists the available
components.  For each shared component we will provide:
+ We will provide a top-level {{{package.html}}} javadoc under {{{java/org/apache/derby/common}}}
that describes the shared components guidelines (once they are approved) and lists the available
components.  For each shared component we will provide:
  
     * Name of component
     * Description of component (its role or intent)
@@ -93, +93 @@

  
  == Introducing New Shared Components and Shared Packages ==
  
- When a developer wishes to introduce a new shared component or a new package within an existing
shared component, this should be put up for a vote.  This is to help ensure that what we are
sharing makes sense and does not accidentally paint us into some kind of architectural corner.
 Adding new classes or methods to an existing shared package does not need to be put up for
a vote.
+ When a developer wishes to introduce a new shared component or a new package within an existing
shared component, this should be put up for a vote.  This is to help ensure that what we are
sharing makes sense and does not accidentally paint us into some kind of architectural corner.
 Adding new classes or methods to an existing shared package does not need to be put up for
a vote but should be reviewed using the standard patch review mechanism.
  

Mime
View raw message