## Extract geronimo-eclipse-plugin-2.2-updatesite.zip and calculate check sum for each files
|## uUpload all the files into update site |
|## uUpload deployable.zip and updatesite.zip in a version sub directory, such as www/people.apache.org/builds/geronimo/eclipse/2.2.1 |
|# (/) Test the staging site by downloading the adapter from it |
# (/) Create the How to install GEP v2.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.2 page, then rename the How to install GEP page to the v2.2.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.
|# (/) Close the staging repository in maven staging site in [Sonatype Nexus Maven Repository Manager|https://repository.apache.org/index.html#welcome] so people reviewing the vote can see your artifacts. |
|# (/) Make sure to start a *\[VOTE\]* thread on the Geronimo dev list. In the vote notice, please include: |
#- The precise names and versions being voted on (e.g. geronimo-eclipse-plugin-2.2-deployable.zip and geronimo-eclipse-plugin-2.2-updatesite.zip)
Before starting the process, make sure these work below has been done:
|Note: These notes are written for release 2.2. Change the version number accordingly for your release!|
|Note: Profile allsubproject is added since GEP 2.1.7 and 2.2.1 to include testsuite module during release but exclude the testsuite execution|
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.2)
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)
NOTE: To generate keys, you need to notice the rules here http://www.apache.org/dev/openpgp.htmland http://www.apache.org/dev/key-transition.html
NOTE: Maven release plugin will generate the signature and checksum for all jar files, but for other files, you need to generate them manually.
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.
If you use FTP to transfer the files to the *Geronimo Eclipse Update Site *make sure to transfer everything in binary mode. Otherwise, the checksum files may not transfer correctly (especially if they are transferred in text mode).