Steps
- Wait one to two weeks after the release of the corresponding Geronimo server
- Copy the trunk to branches using the following command:
For example:
svn copy SRC-URL DEST-URL -m "Reason for this commit"
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.0.0 -m "Prepare for release"
- Checkout or update this branches tree on your machine.
- 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.0.0/</connection> <developerConnection>scm:svn:https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.0.0/</developerConnection> <url>https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.0.0/</url> </scm>
- Update the /assembly/pom.xml to replace the maven-buildnumber-plugin with the geronimodevtools-plugin. It should look something like:
<build> <plugins> <plugin> <artifactId>maven-assembly-plugin</artifactId> <configuration> <finalName>g-eclipse-plugin-${version}</finalName> <descriptors> <descriptor>src/main/assembly/deployable.xml</descriptor> <descriptor>src/main/assembly/updatesite.xml</descriptor> </descriptors> </configuration> <executions> <execution> <phase>package</phase> <goals> <goal>attached</goal> </goals> </execution> </executions> </plugin> </plugins> </build>
- Build the new branches tree that will soon be released
- Build a publicly accessible staging site so that the reviewers can download the plugins and the Geronimo server from it
- 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. g-eclipse-plugin-2.0.0-deployable-RCx.zip and g-eclipse-plugin-2.0.0-updatesite-RCx.zip)
Be certain to use the Release Candidate (RC) acronym in the name as it will not likely pass on the first vote
- 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)
- The precise names and versions being voted on (e.g. g-eclipse-plugin-2.0.0-deployable-RCx.zip and g-eclipse-plugin-2.0.0-updatesite-RCx.zip)
- Make sure to start both a VOTE and a DISCUSS thread on the Geronimo dev list
- Create the staging site from the updatesite zip. The only change necessary is to ensure that the org.apache.geronimo.st.v20.core_2.0.0 plugin points back to the staging site as below:
<extension point="org.eclipse.wst.server.core.installableRuntimes"> <installableRuntime id="org.apache.geronimo.runtime.tomcat.20" featureVersion="2.0.1" featureId="org.apache.geronimo.installableruntime.tomcat.feature" featureSite="http://people.apache.org/~mcconne/releases/staging_site/" <!-- This line was altered --> path="geronimo-tomcat6-jee5-2.0.1.zip"> </installableRuntime> <installableRuntime id="org.apache.geronimo.runtime.jetty.20" featureVersion="2.0.1" featureId="org.apache.geronimo.installableruntime.jetty.feature" featureSite="http://people.apache.org/~mcconne/releases/staging_site/" <!-- This line was altered --> path="geronimo-jetty6-jee5-2.0.1.zip"> </installableRuntime> </extension>
- After it has been approved:
- Publist the results on a RESULTS thread on the Geronimo dev list
- Publish the zip files to the distribution location on people.apache.org here:
/www/people.apache.org/dist/geronimo/eclipse
- Ensure that the files you copy to the distribution directoory have 0755 dir permission and a 0644 file permisison set on them
- Ensure that the files you copy to the distribution directoory have the RCx acronym removed from the filename
- Ensure that this location is updated automatically in the next couple of days with the deployable zip file:
http://apache.org/dist/geronimo/eclipse/
- Move the branches tree to tags using the following command:
For example:
svn mv SRC-URL DEST-URL -m "Reason for this commit".
svn move https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.0.0 https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.0.0 -m "Released"
- Merge changes from tags into trunk to ensure they are in sync (except for the assembly pom.xml described above)
- Update the Apache Geronimo Development Tools Subproject web site below. 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)
http://geronimo.apache.org/development-tools.html
- Cleanup the unstable repo at:
http://people.apache.org/dist/geronimo/eclipse/unstable/
- Administer the GERONIMODEVTOOLS JIRA project to update the released and unreleased versions at:
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS
- Final step is to 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):
TBD when Sachin returns