Geronimo Eclipse Plugin Release Process has been edited by Ted Kirby (Oct 07, 2008).

Change summary:

update tag vs. branch processing at the end, and note choice of next version number in trunk, all to match what the server does.

(View changes)



  1. The plan is to sync Geronimo Eclipse Plugin (GEP) releases with those of the Geronimo server. The goal is to release GEP as soon as possible after the release of the corresponding server.

    Note: These notes are written for release 2.1.2. Change the version number accordingly for your release!

  2. Create the How to install GEP v2.1.2 wiki page. Be sure this includes the pre-reqs. The idea is to have a single page with this release-specific information. In the vote note below, refer to this page, with overrides for the staging site URL. The idea here is to create the install page before hand, and use it for the voting, so that folks will review the doc we'll go live with when the vote passes. There is a How to install GEP page, with children of the various versions. These are for folks who may want to install old versions. When the vote passes, move all it's children to the v2.1.2 page, then rename the How to install GEP page to the v2.1.1 page. Make it a child of the v2.1.2 page. Then, rename the v2.1.2 page to the generic How to install GEP page.
  3. Update the release notes. They are the file PLUGIN_RELEASE-NOTES-2.1.2.txt in trunk.

  4. (/ Copy the trunk to branches using the following command:
    svn copy SRC-URL DEST-URL -m "Reason for this commit"

    For example:

    svn copy
    -m "Prepare for GEP 2.1.2 release"
  5. Checkout or update this branches tree on your machine.

  6. Update the <scm> URLs in the pom.xml to point to the final URL in tags. For example:
  7. Build the new branches tree that will soon be released

  8. Build a publicly accessible staging site so that the reviewers can download the plugins from it. An example staging site is
  9. Copy the deployable and updatesite zip files to the staging site. For example

  10. Create the update site by extracting the updatesite zip to the staging site, for example Also include:
    • Instructions for using the staging site
  11. Put the staging site up for a vote. In the vote notice, please include:
    • The precise names and versions being voted on (e.g. and
      1. Be certain to use the Release Candidate (RC) acronym in the name as it will not likely pass on the first vote
      2. Be certain to use the same version numbers as the Geronimo Server (e.g., 2.1.2)
    • The svn urls to the current source and where the tag will be created
    • The svn revision levels being voted on along with pointers to the source and build output files
    • URL of the staging site (with instructions on how to use it)
    • Eclipse requirements if any (with instructions on how to download them and from where)

  12. Test the staging site by downloading the adapter from it (using the same instructions in previous step)

  13. Make sure to start both a [VOTE] and a [DISCUSS] thread on the Geronimo dev list
    Be certain to get enough binding votes according to the Apache Foundation requirements, which in general stipulates 3 PMC +1 votes (see for more details)
  14. After the vote has been approved:
    • Publish the results on a [RESULTS] reply to the original [VOTE] thread on the Geronimo dev list
    • Publish the staging site, including the and files, and the release notes to the Geronimo Eclipse distribution location on here:
    • Ensure that the version subdirectory is used (e.g., 2.1.2)
    • Ensure that the file(s) you copy to the distribution directory have 0775 dir permission and a 0644 file permission set on them
    • Ensure that the file(s) you copy to the distribution directory have the RCx acronym removed from the filename
    • Ensure that the file(s) you copy have the proper checksum files as well (i.e., .asc, .md5, .sha) using these gpg commands:
      gpg --print-md MD5 [fileName] > [fileName].md5
      gpg --print-md SHA1 [fileName] > [fileName].sha
      gpg --armor --output [fileName].asc --detach-sig [fileName]
    • Similarly, ensure that your GPG public key is in the /www/ file before publishing anything to the distribution location

  15. Ensure that the corresponding Geronimo Eclipse distribution website is updated automatically and properly with the file and the file

  16. Update the Geronimo Eclipse Update Site with the contents of the
    1. /www/
    2. /www/
    3. /www/
    Never delete old releases from the update site – always append to it !! Likewise, do not create a new update site as this will break everyone who has this current site configured, and WTP which uses the update site for the downloadable server adapter support.
    • Ensure that the file(s) you copy to the update site directories have 0755 dir permission and a 0644 file permisison set on them
    • Ensure that the file(s) you copy have the proper checksum files as well (i.e., .asc, .md5, .sha) using these gpg commands:
      gpg --print-md MD5 [fileName] > [fileName].md5
      gpg --print-md SHA1 [fileName] > [fileName].sha
      gpg --armor --output [fileName].asc --detach-sig [fileName]
  17. Ensure that corresponding Geronimo Eclipse Update Site website ( is updated automatically in the next 24 hours with the contents of the file.

  18. Move the branches tree to tags using the following command:
    svn move SRC-URL DEST-URL -m "Reason for this commit".
    For example:
    svn move
    -m "Tagging GEP 2.1.2"
    • Follow what the server does. A maintenance branch for the next dot release (2.1.3) may be created later by copying the 2.1.2 tag to a 2.1.3 branch.
  19. Merge changes from tags into trunk to ensure they are in sync (except for the assembly pom.xml described above)

  20. update the How to Install GEP page(s) as described above.

  21. Update version number in trunk (e.g., 2.1.2 -> 2.1.3)
    • Be careful / give some thought to the next version number. ie, 2.2 vs. 2.1.3. I think the best choice is to follow the server.

  22. Update Geronimo version number in trunk (e.g., 2.1.2 -> 2.1.3-SNAPSHOT)

  23. Rename PLUGIN_RELEASE-NOTES-2.1.2.txt to PLUGIN_RELEASE-NOTES-2.1.3.txt.

  24. Update the Apache Geronimo Development Tools Subproject web site. Please include:
    • Updated Release Notes
    • All Eclipse and WTP prerequisites and download instructions
    • Links to recent, pertinent, and relevant presentations (e.g., Shiva's, EclipseWorld, look for others, etc)

  25. Administer the GERONIMODEVTOOLS JIRA project to update the released and unreleased versions

  26. Update the Geronimo Home Page with a News item that we have an updated Geronimo Eclipse Plugin available

  27. Final step is to update the Geronimo Release Roadmaps with the release date.

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences