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 "ForwardCompatibility" by DavidVanCouvering
Date Thu, 30 Mar 2006 22:43:15 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/ForwardCompatibility

------------------------------------------------------------------------------
     * Jar file names
     * Class names
  
+ == What is an Incompatible Change? ==
+ 
+ What constitutes an incompatible change depends upon the type of interface
+ 
+ '''TODO - Provide definition for "incompatible change"'''
+ 
  == Stability Levels ==
  
  To help describe the types of stability guarantees Derby provides for a given interface,
we identify the following stability levels.  These definitions are inspired by the [http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/
OpenSolaris interface taxonomy]
@@ -97, +103 @@

  
  Interfaces that have been reclassified to Deprecated should be documented in the release
notes.
  
+ A deprecated interface may be removed from the project after four minor and/or major releases.
+ 
  == Interface Table ==
  
  This table describes each of the interfaces Derby provides, and the stability guarantee
we provide for that interface.
@@ -118, +126 @@

  ||Precompiled metadata stored procedures||Private Stable|| ||These may be used by earlier
clients to implement JDBC !DatabaseMetadata calls||
  ||SQL States returned by Derby SQLExceptions||Stable?|| ||There is some debate that these
should be Unstable and that it should be OK to change them across minor releases if a bug
is found.  The argument is that very few developers actually depend on these, and that the
JDBC4 {{{SQLException}}} subclasses are more what people are going to rely upon.  Of course,
in Derby, if you change the underlying SQL State, you may very well end up getting a different
{{{SQLException}}} subclass... [My vote is to make these stable - DVC]||
  ||Error message text||Private|| ||Note that this means canon-based tests can not make claims
that a regression has occurred because the output from error messages has changed||
- ||Install directory hierarchy||Stable?|| ||Script writers may require guarantees as to the
location of files within the system||
+ ||Install directory hierarchy||Unstable|| || ||
  ||Tools (ij, dblook, etc.) command-line name and arguments||Stable|| || ||
  ||Tools class names||Stable|| || ||
  ||Tools stdout||Private|| || ||
  ||Tools stderr||Private|| || ||
  ||Tools error codes||Unstable|| || ||
  ||ij properties||Stable|| || ||
- ||Environment variables used by Derby||Stable|| || ||
+ ||Environment variables used by Derby||Unstable|| || ||
  ||Default port number used by Derby network server||Stable|| || ||
  ||JDBC URL format and driver properties for Derby JDBC drivers||Stable|| || ||
  ||Documented derby properties||Stable|| || ||

Mime
View raw message