Version 42
Created by tom.baeyens on Feb 10, 2006 9:42 AM. Last modified by tom.baeyens on Nov 9, 2007 3:40 AM.

    Prerequisites

    You should have zip and cvs installed on your machine.  In case you have a windows box, these tools can be fetched from the jbpm.dist module.  There is a bin folder with a zip file that contains these tools.

     

    Also you should have a cvs tag name for the version you are about to release.

     

    HEAD (3.2 branch and SOA branch)

     

    z) Integration tests

     

    • JbpmIntegrationTests

     

    a) Preparation

     

    • JIRA preparation

      • Verify that there are none outstanding issues in JIRA against this release. 

      • Update the jpdl/dist/src/main/resources/runtime/release.notes.html (Make sure they include the jira release notes)

     

    • Run the test suite

      • If it's on head, a check of the latest continuous integration build is OK.

      • Otherwise just run the test suites in jpdl/jar and jpdl/enterprise

     

    • Update version properties

      • build/build.properties: properties lib.jbpm.jpdl.version and jbpm.jpdl.cvs.tag

      • jpdl/dist/src/main/resources/suite/designer.version.info.xml

      • jpdl/dist/src/main/resources/suite/designer/workspace/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.jbpm.gd.jpdl.ui.prefs

      • jpdl/dist/src/main/resources/suite/designer/workspace/.metadata/.plugins/org.jbpm.gd.jpdl.ui/jbpm-installations.xml

    • Verify references to the old version with a search

     

    • CVS Label

      • Create or reposition the label jpdl_<<jpdl_version_with_underscores>>.  E.g. jpdl_3_2_alpha1 or jpdl_3_2

     

    b) Producing the downloadable files

    • Verify existence of the cvs tag 'jpdl_<<jpdl_version_with_underscores>>'.

    • Get the label jpdl_<<jpdl_version_with_underscores>> from module jbpm.3 in cvs

    • Verify properties jboss.home and ant.home in build/build.properties.  If necessary, specify updates in ${user.home}/jbpm/build.properties.  The latter file is not part of CVS and will survive CVS updates.

    • Verify the jpdl/dist/src/main/resource/runtime/release.notes.html (Make sure they include the jira release notes)

    • In jpdl/dist, run ant clean.all package.  If you just ran the suite test build for verification, this target was already include and the distribution files will already be present.

    • The files are in jpdl/dist/target and they are called jbpm-jpdl-<version>.zip and jbpm-jpdl-suite-<version>.zip

     

    c) Upload the files to sf.net

    • In jpdl/dist, run ant upload.jpdl.downloadables to upload the jpdl download files to sourceforge.  To do this, you have to put your email address as the value for key sf.net.upload.pwd in file ${user.home}/jbpm/build.properties

    • In sourceforge, create a new release called jbpm-jpdl-

      • Check the number of bytes after uploading to see if the files didn't get corruptted during transfer.
        E.g. jbpm-jpdl-3.2.Alpha1

      • In jpdl/dist, run {font:courier new}ant upload.jpdl.docs{font} to upload the jpdl docs.  To do this, you have to put appropriate values in the keys {font:courier new}ftp.docs.userid{font} and {font:courier new}ftp.docs.password{font}.   If necessary, specify these properties in {font:courier new}${user.home}/jbpm/build.properties{font}.  The latter file is not part of CVS and will survive CVS updates.

      • Make sure the schema files in {font:courier new}jpdl/jar/src/main/java/org/jbpm/jpdl/xml/.xsd{font} are properly published at http://jbpm.org/xsd/.xsd and available online.

      d) Upload the docs

      e) Upload the schema files

      • If it is a final release of a minor version number, notify se -at- jboss -dot- com and services-management -at- jboss -dot- com about the upcoming release
      • Example message:
      • If it is a new minor release, upload the documentation to docs.jboss.com
      • Tell the project lead to mark the release as released in JIRA. (jira doesn't support other people to be authorized)
      • Publish the news

      f) Upload the libraries to repository.jboss.com

      1. Verify that there are none outstanding issues in JIRA against this release. 
      2. If it is a final release of a minor version number, notify se -at- jboss -dot- com and services-management -at- jboss -dot- com about the upcoming release
      3. Get the label 'jbpm_<<jbpm_version_with_underscores>>' from module jbpm.3 in cvs

      4. Verify property jbpm.version in build.properties

      5. Verify version references in src/resources/gpd/version-info.xml

      6. Verify the release.notes.html (Make sure to include the jira release notes)

      7. Verify existence of the cvs tag 'jbpm_<<jbpm_version_with_underscores>>'. Move it if it already exists.

      8. Verify references to the old version with a search
      9. Run the complete test suite (src/java.jbpm.test/org/jbpm/Alltests.java) in eclipse
      10. Run the test suite via ant
      1. Unzip the cvs and zip tools under jbpm.dist/bin/buildtools-win32.zip and have them on your PATH.

      2. Run the build target 'ant checkout-and-create-dist' in jbpm.dist

      3. Take the resulting files for a test drive
        1. Upzip the starters-kit to a directory of your choice

        2. update property eclipse.zip.file in the jbpm-designer/build.properties file

        3. Use the jbpm-designer/build.xml script to install eclipse and the gpd in it

        4. Start the designer with jbpm-designer/designer.bat and the server with jbpm-server/start.bat

      g) Update the download page in the labs project page

      1. Upload the files to ftp://anonymous@upload.sourceforge.net/incoming//anonymous@upload.sourceforge.net/incoming
      2. Release the files with the 'File Releases' option in the sourceforge admin section
        1. jbpm-

      h) Download the distribution files and check if they didn't get corrupted.

      i) Make Noise

      jBPM jPDL 3.2 Released jBPM jPDL is a process language targetted for the Java platform.  It includes a graphical designer, the runtime engine and a web console.  Main focus of the process language is a clean integration with plain Java and task management.  The jPDL runtime engine and database can be easily integrated within your project.  Note that other process languages like e.g. BPEL are made available in the jBPM platform as a separate package. This release includes: ...

      3.1 Branch

      a) Verification

      b) Building the distro

      c) Upload the files to sf.net

      .zip, jbpm-db-.zip and jbpm-starters-kit-.zip files should be put under the package 'a) jBPM 3'

      1. jbpm-gpd... files should be put under the package 'b) jBPM Process Designer'

      2. jbpm-bpel... files should be put under the package 'c) jBPM BPEL extension'

    1. Test the download to check if the files didn't get corrupt

     

    d) Various

    1. If it is a new minor release, upload the documentation to docs.jboss.com

    2. Tell the project lead to mark the release as released in JIRA. (jira doesn't support other people to be authorized)

    3. Publish the news

      1. To the mailing list: jboss-dev and Announcement forums

      2. On the JBoss blog

      3. On the jBPM news in the JBoss website

      4. Main releases might also be posted on the jboss.org home page

      5. http://www.jboss.com/products/jbpm/downloads

     

    10953 Views Categories: Tags: