db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "TomohitoNakayama" <tomon...@basil.ocn.ne.jp>
Subject Re: [Db-derby Wiki] Update of "SharedComponentVersioningGuidelines" by DavidVanCouvering
Date Thu, 13 Oct 2005 13:45:31 GMT
Hello.

I wonder what is "new shared component" , which trigger voting for shared component .

Is it new *.java file to be shared ?
Or new package to be shared ?
Or is it impossible to define and , we need to make culture to distinguish it through cross
reviewing patches ?

// I think the last option is mostly like apache way ....

Best regards .

/*

         Tomohito Nakayama
         tomonaka@basil.ocn.ne.jp
         tomohito@rose.zero.ad.jp
         tmnk@apache.org

         Naka
         http://www5.ocn.ne.jp/~tomohito/TopPage.html

*/
----- Original Message ----- 
From: "Apache Wiki" <wikidiffs@apache.org>
To: <derby-commits@db.apache.org>
Sent: Thursday, October 13, 2005 12:57 AM
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
>
> ------------------------------------------------------------------------------
>
>  However, to keep a very simple user experience, when we create a release, the classes
in the shared component JAR files will be 
> merged into derby.jar and derby-client.jar.
>
> -
>
> + == Introducing New Shared Components ==
> +
> + Any new shared component, or a significant addition to an existing shared component,
that a developer wishes to introduce 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.
> +
>
> 


Mime
View raw message