Home > Apache Geronimo Project Management > Documentation > Release Eclipse Plugin Process
Apache Geronimo Project Management
Release Eclipse Plugin Process
Edit Page   Browse Space   Add Page   Add News

Steps

  1. Wait one to two weeks after the release of the corresponding Geronimo server

  2. Make sure that the ant script that is used to download the Eclipse artifacts (i.e., build.xml) only contains released versions – not maintenance versions of Eclipse, DTP, EMF, GEF, WTP, etc.

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

    For example:

    svn copy https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/trunk
         https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.1.2 -m "Prepare for GEP 2.1.2 release"

  4. Checkout or update this branches tree on your machine.

  5. Update the <scm> URLs in the pom.xml to point to the final URL in tags. For example:
    <scm>
     <connection>scm:svn:https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.2/</connection>
     <developerConnection>scm:svn:https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.2/</developerConnection>
     <url>https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.0/</url>
</scm>

  6. Build the new branches tree that will soon be released

  7. Build a publicly accessible staging site so that the reviewers can download the plugins and the Geronimo server from it

  8. Copy the deployable zip file, and the updatesite zip file to a publicly accessible location. Put them up for a vote. In the vote notice, please include:
    • The precise names and versions being voted on (e.g. geronimo-eclipse-plugin-2.1.1-deployable-RCx.zip and geronimo-eclipse-plugin-2.1.1-updatesite-RCx.zip)
      Tips
      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.x)
    • 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)
    • WTP requirements if any (with instructions on how to download them and from where)

  9. Create the staging site from the updatesite zip. Also include:
    • Instructions for using the staging site
    • Release notes

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

  11. Make sure to start both a VOTE and a DISCUSS thread on the Geronimo dev list

    • Be certain to use the same version numbers as the Geronimo Server (e.g., 2.1.2)
      Tip
      Be certain to get enough binding votes according to the Apache Foundation requirements, which in general stipulates 3 PMC +1 votes (see http://www.apache.org/foundation/voting.html#ReleaseVotes for more details)
  12. After it has been approved:
    • Publish the results on a RESULTS reply to the original VOTE thread on the Geronimo dev list
    • Publish the deployable zip file to the distribution location on people.apache.org here: 
      /www/www.apache.org/dist/geronimo/eclipse
      Warning
      Do not publish the deployable zip file that is on the staging site since that points back to the staging site !! There should be a deployable zip that is on the staging site and another deployable zip that is reviewed for release.
    • Ensure that the version subdirectory is used (e.g., 2.1.1)
    • 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 deployable zipfile and the release notes are included in this directory (http://people.apache.org/dist/geronimo/eclipse/)
    • 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]
    • Similiarly, ensure that your GPG public key is in the /www/www.apache.org/dist/geronimo/KEYS file before publishing anything to the distribution location

  13. Ensure that the production distribution site is updated automatically properly with the deployable zip file

  14. Update the distribution Update Site with the contents of the updatesite.zip:
    /www/www.apache.org/dist/geronimo/eclipse/updates/features
/www/www.apache.org/dist/geronimo/eclipse/updates/plugins

    Warning
    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]
    • Augment the existing site.xml file from the update site to include all the new features, plugins, and references to the corresponding Geronimo server
      Why is the site.xml from the updatesite.zip file not used instead ?? Process improvement possible here (see GERONIOMODEVTOOLS-227).
      This will be changing for GEP 2.1.2.

  15. Ensure that production Update Site is updated automatically in the next 24 hours with the contents of the upatesite.zip file

  16. Copy (do not move as the branch needs to remain for future maintenance) the branches tree to tags using the following command: 
    svn copy SRC-URL DEST-URL -m "Reason for this commit".

    For example:

    svn copy https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.1.1
         https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.0 -m "Tagging GEP 2.1.1"

  17. Merge changes from tags into trunk to ensure they are in sync (except for the assembly pom.xml described above)

  18. Update version number in trunk (e.g., 2.1.0 -> 2.1.1)

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

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

  21. Cleanup the unstable repo

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

  23. Update appropriate remote Eclipse download site(s) so users can download the Geronimo server and the Geronimo Eclipse plugin from within Eclipse (without having to add a new "Remote Site" from the Eclipse Help panels)

  24. Final step is to update the Geronimo Home Page with a News item that we have an updated Geronimo Eclipse Plugin available

Copyright © 2003-2007, The Apache Software Foundation