Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Steps

  1. (error) (tick) Wait one to two weeks after the release of the corresponding Geronimo server

  2. (error) (tick) 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. (error) Copy the trunk to branches using the following command:
    Code Block
    svn copy SRC-URL DEST-URL -m "Reason for this commit"
    
    For example:
    Code Block
    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.12 -m "Prepare for GEP 2.1.12 release"
    

  4. (error) Checkout or update this branches tree on your machine.

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

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

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

  8. (error) 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)
      Tip
      titleTips

      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. (error) Create the staging site from the updatesite zip. The only change necessary is to ensure that the org.apache.geronimo.st.v21.core_2.1.0 plugin points back to the staging site as below:
    Code Block
    <extension point="org.eclipse.wst.server.core.installableRuntimes">
        <installableRuntime id="org.apache.geronimo.runtime.tomcat.21"
            featureVersion="2.1.1"
            featureId="org.apache.geronimo.installableruntime.tomcat.feature"
            featureSite="http://people.apache.org/~mcconne/releases/staging_site/"      <!-- This line was altered -->
            path="geronimo-tomcat6-javaee5-2.1.1.zip">
        </installableRuntime>
        <installableRuntime id="org.apache.geronimo.runtime.jetty.21"
            featureVersion="2.1.1"
            featureId="org.apache.geronimo.installableruntime.jetty.feature"
            featureSite="http://people.apache.org/~mcconne/releases/staging_site/"      <!-- This line was altered -->
            path="geronimo-jetty6-javaee5-2.1.1.zip">
        </installableRuntime>
    </extension>
    

  10. (error) Test the staging site:
    • (error) Testcase 1: Download the adapter (by pointing to the new staging site)
    • (error) Testcase 2: Download the Tomcat server (all versions supported by this GEP release)
    • (error) Testcase 3: Download the Jetty server (all versions supported by this GEP release)
    • (error) Testcase 4: From a clean/fresh Eclipse installation, build the adapter, import the plugins, download and install Tomcat and Jetty server (all versions supported by this GEP release)

  11. (error) 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.1)
      Tip
      titleTip

      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)

...