Release Guide has been edited by Kevin Menard (Jan 10, 2007).

(View changes)

Content:

Note that this page is of use for committers only. It describes the general procedure of building a Cayenne release.

  • Create a report in Jira listing all issues that are FIXED but not CLOSED, paste its contents to RELEASE-NOTES-[version].txt. Bulk-close all such issues.
  • Tag cayenne directory under the repository trunk (assuming [release_version] is a version tag identifying the release, such as "1.2B3"):
svn mkdir https://svn.apache.org/repos/asf/incubator/cayenne/main/tags/[release_version] -m "[release_version] tag dir"
svn copy https://svn.apache.org/repos/asf/incubator/cayenne/main/trunk/cayenne \
   https://svn.apache.org/repos/asf/incubator/cayenne/main/tags/[release_version]/cayenne -m "tagging B3 release"

  • Export the new tag to some directory on the build machine:
svn export https://svn.apache.org/repos/asf/incubator/cayenne/main/tags/[release_version]/cayenne
  • Change project.version build property to reflect current release version:
cd cayenne/cayenne-ant
vi default.properties
  • Run a test to make sure the checkout is ok:
ant test

Test with all supported databases listed here, or at least as many as possible. See Legacy Ant Unit Tests for more details on how to test each of the various database servers with legacy versions of Cayenne.

  • Build a release for the target platform:
ant release
ant release-win
ant release-mac
  • Signing release

For more info visit this page. Release manager key must be in the project KEYS file. Signing is a manula procedure not included in the Ant or Maven script. Here is how it might work ("-u" option can be ommitted if you have only one GPG key):

gpg --armor -u B8AF90BF --output cayenne-2.0-incubating-SNAPSHOT.tar.gz.asc --detach-sig cayenne-2.0-incubating-SNAPSHOT.tar.gz

Reply via email to