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 Wed, 18 Jul 2007 00:17:01 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

------------------------------------------------------------------------------
  
    See TODO in #8 for caveat concerning the beta flag. Don't forget to post to derby-dev
requesting that a new version be added to JIRA for the next version of Derby.
  
-  1. Bump the third version number, adjust the beta flag, finalize CHANGES, and check in
the new version and test masters. Also adjust version numbers in documentation by modifying
the appropriate *conrefs.dita files.
+  1. Bump the third version number, adjust the beta flag, finalize CHANGES, and check in
the new version and test masters. You will need to clobber and build to see the changed release
number(s) reflected in the source. Note that the first release off a new branch is automatically
beta, even if you set the beta flag in tools/ant/properties/release.properties to false. Also
adjust version numbers in documentation by modifying the appropriate *conrefs.dita files.
  
    There is not currently an ant target for bumping the third version number. The third and
fourth parts of the version are combined into a single property, maint, where maint = (third
digit * 1000000) + fourth digit. Also, if this is a major/minor (feature) release, you should
remove the beta flag at this time. You should update tools/ant/properties/release.properties
by hand and then run:
  
@@ -126, +126 @@

    {{{cd tools/release
  ant regex.masters}}}
  
+   TODO: the regex.masters target does not currently account for changes in the beta flag.

-   TODO: the regex.masters target does not currently account for changes in the beta flag.
If you are creating the first release off of a new branch, do not forget to set the beta flag
in tools/ant/properties/release.properties to false.
- Note that you may need to do ant clobber to test out changes to the releaselproperties with
for instance sysinfo.
  
   1. Generate RELEASE_NOTES.html in the branch and check it into the svn repository.
  
@@ -152, +151 @@

  
   1. Build the documentation, or grab a copy from the website.
  
-   The documentation needs to be included in the -bin distribution, so you will need a copy
of the documentation ready when running the ant release target. Information on building the
docs is located at [http://db.apache.org/derby/manuals/dita.html]. Another option, if your
release is from the main branch or the docs have not been branched yet, is to log in to people.apache.org
and grab the current uploaded copy on the website, in /www/db.apache.org/derby/docs/. Tar
up the correct version of the docs into your home directory (don't leave a big tarfile in
/www/db.apache.org/derby/docs please!) and download it to your local machine with sftp. Untar
it to a local directory, that is not inside your subversion view where you are building the
release or it will be included in the -src distribution built by the release target.
+   The documentation needs to be included in the -bin distribution and src, so you will need
to access the doc branch when running the ant release target. Information on building the
docs is located at [http://db.apache.org/derby/manuals/dita.html]. 
  
   1. Copy packaging.tmpl to packaging.properties in tools/release and modify as necessary.
  

Mime
View raw message