Administrator Administrator [http://community.jboss.org/people/admin] modified the document: "jBPM3 Release Procedure" To view the document, visit: http://community.jboss.org/docs/DOC-13428 -------------------------------------------------------------- h3. Get clean Hudson matrices Create Hudson jobs for the release branch in the http://jbpm.dyndns.org:8180/hudson/ QA box. # su -l hudson $ cd svn/jbpm/jbpm3/branches/ $ svn co http://anonsvn.jboss.org/repos/jbpm/jbpm3/branches/jbpm-3.x $ cd jbpm-3.x/hudson $ ant hudson-setup Run the jobs and verify they complete successfully. h3. Follow web console test protocol Refer to http://community.jboss.org/docs/DOC-13416 jBPM3 Web Console Test Protocol h3. Update Release Notes Copy the release notes from the JIRA https://jira.jboss.org/jira/browse/JBPM?report=com.atlassian.jira.plugin.... road map into modules/distribution/src/main/etc/release.notes.html h3. Create tag in Subversion $ svn cp https://svn.jboss.org/repos/jbpm/jbpm3/branches/jbpm-3.x https://svn.jboss.org/repos/jbpm/jbpm3/tags h3. Deploy maven artifacts Check out the jBPM3 maven artifacts. $ mkdir -p repository/org/jbpm $ cd repository/org/jbpm $ svn co https://svn.jboss.org/repos/repository.jboss.org/maven2/org/jbpm/jbpm3 Define the following profile in your http://maven.apache.org/settings.html settings.xml. Set property altDeploymentRepository to the location where you checked out the jBPM 3 maven artifacts. <profile>   <id>personal-profile</id>   <activation>     <property>       <name>user.name</name>     </property>   </activation>   <properties>           <altDeploymentRepository>repository.jboss.org::default::file:${user.home}/jbpm/jbpm3/repository</altDeploymentRepository>     <updateReleaseInfo>true</updateReleaseInfo>   </properties> </profile> Change to the project directory and execute the command below. This will put the new artifacts in your local checkout of the repository, update the artifact metadata and calculate the checksums. $ mvn -Pdistro clean deploy Review the generated artifacts and commit when you are satisfied. After a few minutes, the artifacts will be available from the JBoss http://repository.jboss.org/maven2/org/jbpm/jbpm3/ repository. h3. Release files for download See the http://p.sf.net/sourceforge/frs Guide to the File Release System for a complete description of the procedure. Here is a quick reference. SF.net offers several methods to upload files, including http://apps.sourceforge.net/trac/sourceforge/wiki/SCP SCP. The username below corresponds to your SF.net account. $ cd modules/distribution/target $ scp jbpm-installer-version.jar username@frs.sourceforge.net:uploads Point your browser to the https://sourceforge.net/project/admin/editpackages.php?group_id=70542 file releases page. Add a new release and associate the uploaded file to it. h3. Publish new version in the downloads page Check out the jBPM portal content. $ svn co https://cms.labs.jboss.com/prod/forge/portal-content/default/members/jbos... Update and commit the following files. The corresponding download pages will be refreshed shortly afterwards. || *Portal Content File * || *Download Page* || | freezone/jbpm/downloads.html | http://www.jboss.org/jbossjbpm/jbpm_downloads/ | | freezone/jpdl/downloads.html | http://www.jboss.org/jbossjbpm/jpdl_downloads/ | Good luck. -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-13428] Create a new document in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&am...]