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 MyrnavanLunteren
Date Tue, 24 Jul 2007 17:44:20 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

------------------------------------------------------------------------------
- == 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.#2 Run the snapshot target.
- 
-  At the top of your subversion view of the trunk or one of the branches, do:
- 
-  {{{svn up
- ant clobber
- rm -rf jars javadoc snapshot    # make sure everything is cleaned out
- ant sane ; ant all ; ant buildjars   # for the debug archives
- ant clobber
- ant insane
- ant -Dsane=false snapshot}}}
- 
-  It is best to do this in a view where there are no modified files or mixed revisions. This
will create a snapshot directory at the top level, which will contain the five snapshot files:
- 
-   * db-derby-snapshot-[version]-[changenumber].tar.gz
-   * db-derby-snapshot-[version]-[changenumber].zip
-   * db-derby-snapshot-debug-[version]-[changenumber].tar.gz
-   * db-derby-snapshot-debug-[version]-[changenumber].zip
-   * derby_core_plugin_[version]_[changenumber].zip
- 
- The need to run 'ant insane' as a separate step before the snapshot is filed in JIRA as
DERBY-744.
- 
-  1.#3 Update the website.
- 
-  For instructions on how to build the website using Forrest, please see:
- 
-  http://db.apache.org/derby/papers/derby_web.html
- 
-   a. Place the five files created by the snapshot target into the src/documentation/content/xdocs/binaries
directory of the location to which you checked out the website source. 'svn add' them, and
'svn delete' any old snapshot that the new snapshot is replacing. Don't forget to 'svn add'
the files in the build part of the site tree.
- 
-  b. Update the derby_downloads.xml page in the src/documentation/content/xdocs directory
so that the links to the current snapshot point to your new files.
- 
-  c. Run 'forrest site' at the top of the site tree.
- 
-  d. Check the changes. If they look good, 'svn commit' them. NOTE: you should revert any
changed files in build/tmp or build/site/skin. Also, please {{{svn delete}}} any old snapshot
files that are no longer necessary.
- 
-  e. Update the website on people.apache.org by logging into the machine and doing:
- 
-  {{{cd /www/db.apache.org/derby
- svn up}}}
- 
-  Note that people.apache.org is rsync'd to the actual website every hour or so. Verify that
the changes appear on the Derby website at http://db.apache.org/derby/derby_downloads.html
- 
-  1.#4 Bump the version number.
- 
-  In the tools/release directory, run the Ant bumplastdigit target.
- 
-  {{{cd tools/release
- 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/desire to have a release on the list
@@ -401, +338 @@

  
    Update STATUS to reflect that the release has occurred. Check in the new file. You're
done!
  
+ 
+ == 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.#2 Run the snapshot target.
+ 
+  At the top of your subversion view of the trunk or one of the branches, do:
+ 
+  {{{svn up
+ ant clobber
+ rm -rf jars javadoc snapshot    # make sure everything is cleaned out
+ ant sane ; ant all ; ant buildjars   # for the debug archives
+ ant clobber
+ ant insane
+ ant -Dsane=false snapshot}}}
+ 
+  It is best to do this in a view where there are no modified files or mixed revisions. This
will create a snapshot directory at the top level, which will contain the five snapshot files:
+ 
+   * db-derby-snapshot-[version]-[changenumber].tar.gz
+   * db-derby-snapshot-[version]-[changenumber].zip
+   * db-derby-snapshot-debug-[version]-[changenumber].tar.gz
+   * db-derby-snapshot-debug-[version]-[changenumber].zip
+   * derby_core_plugin_[version]_[changenumber].zip
+ 
+ The need to run 'ant insane' as a separate step before the snapshot is filed in JIRA as
DERBY-744.
+ 
+  1.#3 Update the website.
+ 
+  For instructions on how to build the website using Forrest, please see:
+ 
+  http://db.apache.org/derby/papers/derby_web.html
+ 
+   a. Place the five files created by the snapshot target into the src/documentation/content/xdocs/binaries
directory of the location to which you checked out the website source. 'svn add' them, and
'svn delete' any old snapshot that the new snapshot is replacing. Don't forget to 'svn add'
the files in the build part of the site tree.
+ 
+  b. Update the derby_downloads.xml page in the src/documentation/content/xdocs directory
so that the links to the current snapshot point to your new files.
+ 
+  c. Run 'forrest site' at the top of the site tree.
+ 
+  d. Check the changes. If they look good, 'svn commit' them. NOTE: you should revert any
changed files in build/tmp or build/site/skin. Also, please {{{svn delete}}} any old snapshot
files that are no longer necessary.
+ 
+  e. Update the website on people.apache.org by logging into the machine and doing:
+ 
+  {{{cd /www/db.apache.org/derby
+ svn up}}}
+ 
+  Note that people.apache.org is rsync'd to the actual website every hour or so. Verify that
the changes appear on the Derby website at http://db.apache.org/derby/derby_downloads.html
+ 
+  1.#4 Bump the version number.
+ 
+  In the tools/release directory, run the Ant bumplastdigit target.
+ 
+  {{{cd tools/release
+ 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.
+ 

Mime
View raw message