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.
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
Alternatively, the file upload can be done manually to ftp://anonymous@upload.sourceforge.net/incoming
In sourceforge, create a new release called jbpm-jpdl-{version} E.g. jbpm-jpdl-3.2.Alpha1
Check the number of bytes after uploading to see if the files didn't get corruptted during transfer.
d) Upload the docs
In jpdl/dist, run ant upload.jpdl.docs to upload the jpdl docs. To do this, you have to put appropriate values in the keys ftp.docs.userid and ftp.docs.password. If necessary, specify these properties in ${user.home}/jbpm/build.properties. The latter file is not part of CVS and will survive CVS updates.
e) Upload the schema files
Make sure the schema files in jpdl/jar/src/main/java/org/jbpm/jpdl/xml/*.xsd are properly published at http://jbpm.org/xsd/*.xsd and available online.
f) Upload the libraries to repository.jboss.com
g) Update the download page in the labs project page
h) Download the distribution files and check if they didn't get corrupted.
i) Make Noise
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:
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:
...
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
To the mailing list: jboss-dev and Announcement forums
On the JBoss blog
On the jBPM news in the JBoss website
Main releases might also be posted on the jboss.org home page
Verify that there are none outstanding issues in JIRA against this release.
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
Get the label 'jbpm_<<jbpm_version_with_underscores>>' from module jbpm.3 in cvs
Verify property jbpm.version in build.properties
Verify version references in src/resources/gpd/version-info.xml
Verify the release.notes.html (Make sure to include the jira release notes)
Verify existence of the cvs tag 'jbpm_<<jbpm_version_with_underscores>>'. Move it if it already exists.
Verify references to the old version with a search
Run the complete test suite (src/java.jbpm.test/org/jbpm/Alltests.java) in eclipse
Run the test suite via ant
b) Building the distro
Unzip the cvs and zip tools under jbpm.dist/bin/buildtools-win32.zip and have them on your PATH.
Run the build target 'ant checkout-and-create-dist' in jbpm.dist
Take the resulting files for a test drive
Upzip the starters-kit to a directory of your choice
update property eclipse.zip.file in the jbpm-designer/build.properties file
Use the jbpm-designer/build.xml script to install eclipse and the gpd in it
Start the designer with jbpm-designer/designer.bat and the server with jbpm-server/start.bat
c) Upload the files to sf.net
Upload the files to ftp://anonymous@upload.sourceforge.net/incoming
Release the files with the 'File Releases' option in the sourceforge admin section
jbpm-{version}.zip, jbpm-db-{version}.zip and jbpm-starters-kit-{version}.zip files should be put under the package 'a) jBPM 3'
jbpm-gpd... files should be put under the package 'b) jBPM Process Designer'
jbpm-bpel... files should be put under the package 'c) jBPM BPEL extension'
Test the download to check if the files didn't get corrupt
d) Various
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
To the mailing list: jboss-dev and Announcement forums
On the JBoss blog
On the jBPM news in the JBoss website
Main releases might also be posted on the jboss.org home page
)