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] Trivial Update of "DerbySnapshotOrRelease" by AndrewMcIntyre
Date Wed, 12 Oct 2005 23:16:24 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 AndrewMcIntyre:
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

------------------------------------------------------------------------------
  == Snapshots ==
+  1. Update CHANGES.
+ 
+  Edit the CHANGES file to include a list of the bug fixes included in the snapshot. It is
not necessary to make an exhaustive list of subversion commits. Only changes that would be
visible to a user need to be included.
+ 
-  1. Run the snapshot target.
+  1.#2 Run the snapshot target.
  
   At the top of your subversion view of the trunk or one of the branches, do:
  
@@ -14, +18 @@

    * db-derby-[version]-[changenumber].zip
    * derby_core_plugin_[version]_[changenumber].zip
  
-  1.#2 Update the website.
+  1.#3 Update the website.
  
   For instructions on how to build the website using Forrest, please see:
  
@@ -35, +39 @@

  
   The public Derby website updates roughly every two hours. Check that the site has updated
properly after that amount of time has passed.
  
-  1.#3 Bump the version number.
+  1.#4 Bump the version number.
  
   In the tools/release directory, run the Ant bumplastdigit target.
  
@@ -43, +47 @@

  ant bumplastdigit}}}
  
   This target updates tools/ant/properties/release.properties and several test canons that
contain the version number. Check that the version number is correct. 'svn commit' the changed
files.
+ 
+  1.#5 Announce to the lists.
+ 
+  It's a good idea, once the snapshot has appeared on the site, to announce to derby-dev
and derby-user that the new snapshot has been posted so interested testers can grab it.
+ 
+  Also, a new JIRA version will need to be created for the new, bumped version number. An
email to derby-dev stating that you've bumped the version will (hopefully) be sufficient to
get the attention of one of the Derby JIRA admins to add a new version in JIRA.
  
  Releases
   1. Announce your intention to have a release on the list

Mime
View raw message