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 "DerbySnapshotOrRelease" by MyrnavanLunteren
Date Fri, 15 Jun 2007 16:03:57 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 MyrnavanLunteren:
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

------------------------------------------------------------------------------
    All features and bug fixes should be tracked in JIRA: http://issues.apache.org/jira/browse/DERBY
    Mark the Fix In field for the JIRA entries for the items you want to be in the release
with the proper version. Also, it's a good idea to post to derby-dev to get an idea of what
features or fixes other contributors would like in the release.
  
-  1. Fix the bugs, update STATUS and CHANGES as needed
+  1. Fix the bugs, update STATUS and CHANGES/RELEASE_NOTES.html as needed
  
    Get to work! Add features, fix bugs, and update STATUS as you go. The wiki is nice, as
are personal webpages, but STATUS is the designated place for Apache projects to keep their
current status. Apache members and committers expect to be able to grab the STATUS file from
the code tree to determine the current status of the project. It's a nice thing to keep the
STATUS file on branches up to date with the current status of the branch. The other essential
document is a document describing the changes. Derby branches up to 10.2 included a file 'CHANGES'
for that purpose; 10.3 branch and trunk have a RELEASE_NOTES.html checked in. RELEASE_NOTES.html
is generated using the generator in <10.3 branch and up/trunk>/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java.
  
@@ -91, +91 @@

      - resolved to 'Fixed'
      - fixed in the release under study but not in the previous release
      - marked with 'Existing Application Impact' or 'Release Note Needed'.
+ 
+  1. Check that all creative works have ASF license headers. See: [http://wiki.apache.org/db-derby/FixingLicenseHeader]
+ 
  
   1. Make sure your public PGP/GPG key is in the KEYS file 
  

Mime
View raw message