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 |
www/people.apache.org/builds/geronimo/eclipse/updates |
1. Be certain to use the Release Candidate (RC) acronym in the name as it will not likely pass on the first vote |
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) |
/www/www.apache.org/dist/geronimo/eclipse |
gpg --print-md MD5 [fileName] > [fileName].md5 gpg --print-md SHA1 [fileName] > [fileName].sha gpg --armor --output [fileName].asc --detach-sig [fileName] |
1. /www/www.apache.org/dist/geronimo/eclipse/updates/features 2. /www/www.apache.org/dist/geronimo/eclipse/updates/plugins 3. /www/www.apache.org/dist/geronimo/eclipse/updates/site.xml |
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). |