[jboss-user] [jBPM] - jBPM3 Release Procedure

[Alejandro Guizar]

Alejandro Guizar [http://community.jboss.org/people/alex.guizar%40jboss.com] 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.system.project:roadmap-panel road map into modules/distribution/src/main/etc/release.notes.html
h3. Tag and Deploy Maven Artifacts
To deploy to the JBoss Maven repository, you will need to add your credentials to your  http://maven.apache.org/settings.html settings.xml file.
<settings>
  <servers>
    <server>
      <id>jboss-snapshots-repository</id>
      <username>jboss.org username</username>
      <password>jboss.org password</password>
    </server>
    <server>
      <id>jboss-releases-repository</id>
      <username>jboss.org username</username>
      <password>jboss.org password</password>
    </server>
  </servers>
</settings>

 http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html Prepare for release with the following command. Maven will prompt for the release version (say, 3.2.10), the SCM release tag (jbpm-3.2.10) and the next development version (3.2.11-SNAPSHOT).
$ mvn release:prepare

Once you are ready to  http://maven.apache.org/plugins/maven-release-plugin/examples/perform-release.html perform the release, execute:
$ mvn release:perform

After the release is performed, Nexus will automatically create a temporary staging repository. Refer to  http://community.jboss.org/docs/DOC-15179 Maven Deploying a Release for details on closing the staging 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 at 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
TBD
--------------------------------------------------------------

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&containerType=14&container=2034]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20110208/58dcf318/attachment-0001.html