|## mvn release:prepare |
## mvn release:perform
|# (/) Set up a staging site for verifying update site at people.apache.org. Eg. [http://people.apache.org/builds/geronimo/eclipse/updates/|http://people.apache.org/builds/geronimo/eclipse/updates/], this staging site locates at www/people.apache.org/builds/geronimo/eclipse/updates directory on people.apache.org server |
|## Extract geronimo-eclipse-plugin-2.2-updatesite.zip and calculate check sum for each files |
## upload all the files into update site
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!|
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).