Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: derby-commits@db.apache.org
Date: Wed, 05 Oct 2005 00:07:01 -0000
Message-ID: <20051005000701.30407.39478@ajax.apache.org>
Subject: [Db-derby Wiki] Update of "SharedComponentVersioningGuidelines" by
 DavidVanCouvering

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

------------------------------------------------------------------------------
  ## page was renamed from ModuleVersioningGuidelines
  ## page was renamed from ModuleVersioningPolicy
  
- Review comments for these guidelines can be created, viewed and responded to at ModuleVersioningGuidelinesReview
+ Review comments for these guidelines can be created, viewed and responded to at SharedComponentVersioningGuidelinesReview
  
  This document describes our guidelines around shared components in Derby, where a shared component is a collection of one or more packages that is used across multiple subsystems within Derby. Very loosely, I would define a "subsystem" as the code contained in one of the top-level source directories, e.g. engine, client, drda, tools, etc.  As of this writing, the only shared component like this is the proposed common code component (see [http://issues.apache.org/jira/browse/DERBY-289  DERBY-289]).  Other components may be defined in the future as needed (for example, perhaps the DRDA networking code should be separated out as an independent shared component).