|## Add the new plugin catalog file into svn repository at url \-> [https://svn.apache.org/repos/asf/geronimo/site/trunk/docs/plugins] |
The changes will be automatically sync with /www/geronimo.apache.org/plugins
|# Once release vote pass, you need to prepare a release message to publish to geronimo web site. site: |
|* Open Apache Geronimo site: [https://cwiki.apache.org/confluence/display/GMOxSITE/], click " Add Blog Post", then post a release message. After it's complete, ask Jeff to synchronize this page |
|*Notes:* After you create gpg public/private key, and update public key to [https://svn.apache.org/repos/asf/geronimo/KEYS], you also have to update public key in file [http://www.apache.org/dist/geronimo/KEYS], which should keep consistent with KEYS file in svn. [http://www.apache.org/dist/geronimo/KEYS] is located at people.apache.org server: |
Notes: After you create gpg public/private key, and update public key to https://svn.apache.org/repos/asf/geronimo/KEYS, you also have to update public key in file http://www.apache.org/dist/geronimo/KEYS, which should keep consistent with KEYS file in svn. http://www.apache.org/dist/geronimo/KEYS is located at people.apache.org server:
cp KEYS KEYS.006
cat [your_keys_file] >> KEYS
Half hour later, this will be synchronized to http://www.apache.org/dist/geronimo/KEYS.
Except this, upload your gpg public key to pgp.mit.edu website.
If not, when you close staging repository, there may be no public key error.