Page History

...

Ask on the dev list if you need help with these steps.

...

Remove previous release from mirrors

...

1. Update links to previous releases that appear on https://geode.apache.org/releases/.  The finalize_release script may have removed some old version from the mirror site, if so, the links on the "downloads" web page should be changed to point to the archive site instead

...

1. update https://geode.apache.org/releases/

   , i.e.

   1. change the links ( for any old versions removed by finalize_release.sh , not the one you just released!) that contain closer.cgi to archive, e.g.that contain closer.cgi to archive, e.g.:
      1. before: http://apache.org/dyn/closer.cgi/geode...
      2. after: http://archive.apache.org/dist/geode...
   2. change the .asc/.sha256 links like this:
      1. before: httphttps://www.apache.org/dyndist/closer.cgi/geode...
      2. after: httphttps://archive.apache.org/dist/geode...
2. Build website from sources as described in geode-site/website/README.md..change the links for the gpg/md5 links like this:
3. before: https://www.apache.org/dist/geode...
after: https://archive.apache.org/dist/geode..
4. In the generated site, create the directory geode-site/content/releases/latest.
5. Obtain a copy of the javadoc directory from the binary release and put it in the geode-site/content/releases/latest directory (link from the website's Docs landing page points to ../releases/latest/javadoc).
6. Deploy the generated site by checking it into the asf-site branch of the apache-geode repo.
   
   

Update dependencies

Now is the best time to bump dependency versions on the various 3rd-party libraries used by Geode.  Start a DISCUSS thread asking for a volunteer to lead this effort.

...