The following tasks need to be done to support the distribution of AOO 3.4 once its release is approved.

  1. Start populating the mirrors with the approved AOO 3.4 images.  This could take 24 hours or more.  So start this in parallel with the other activities.

    (joes, galoppini, done)

  2. Submit the AOO URL's and SHA256 hashes to Symantec to "whitelist" us in their anti-virus:  https://submit.symantec.com/whitelist/isv/new/

    (robweir, done)

  3. Disable the downloads directly from www.openoffice.org.  Instead have the download link go to download/index.html

    (robweir, done)

  4. Make a copy of the the older MirrorBrain-enabled download/index.html page.  Put them in a download/legacy directory.  Add a disclaimer notice that these are not Apache releases, but legacy releases under a different license.

    (marcus, done)

  5. Make a copy of the the older MirrorBrain-enabled download/other.html page.  Put them in a download/legacy directory.  Add a disclaimer notice that these are not Apache releases, but legacy releases under a different license.

    (marcus, done)

  6. Update download/index.html pages to SourceForge download locations for AOO 3.4. Establish a test period for these new links. Test with various user agent configurations and languages.

    (kay, done)

  7. Update download/other.html pages to SourceForge download locations for AOO 3.4. Establish a test period for these new links. Test with various user agent configurations and languages.

    (marcus, done

  8. Create a new checksums page for 3.4 release.

    (marcus, done)

  9. Location for source artifact linked from other.html?

    (marcus, done)

  10. Update install guide if needed.

    (kay, done)

  11. Create a new release notes page for 3.4.0 ref on: http://www.openoffice.org/development/releases/

    (kay, done)

  12. Consult with infra regarding the use of the standard "closer.cgi" to access mirrors. Since we are doing mirror site selection via JS, is there a problem with using this? And if so, what do we do instead?

    (dave, done - Joe provided aoo-closer.cgi)

  13. Update branding of download/index.html and download/other.html to "Apache OpenOffice" rather than OpenOffice.org

    (kay, done)

  14. Check and update license (and other) links on the "new" download page.

    (kay, might need more investigation but maybe OK???)

  15. Add text to these pages (or a new page linked to from download/index.html and download/other.html) linking to the hash and signature files explaining how to verify them.  Look at the Apache httpd project's download page for example text.  Note:  links to the hashes and signatures must go to the Apache /dist copy of these files only, not to the mirrors.

    (marcus, done

    , HowTo's for Windows and ASC / KEYS needs still to be done, any volunteers?)

  16. Point downloads from the Mac porting page and subpages to the download webpages.

    (marcus, done)

  17. Make sure that users with browser language "en-GB" are pointed to "download/other.hml" (see "download/languages.js").

    (marcus, done)

  18. Manually update the downloads from the Arabic NL homepage
  19. Manually update the downloads from the Czech NL homepage
  20. Manually update the downloads from the German NL homepage (nfiala, rbircher)
  21. Manually update the downloads from the Spanish NL homepage

    (arielch, done) Links directly to the main /download/ page. Translation in discussion)

  22. Manually update the downloads from the French NL homepage (oooforum@free.fr)
  23. Manually update the downloads from the Hungarian NL homepage (r4zoli)
  24. Manually update the downloads from the Galacian NL homepage
  25. Manually update the downloads from the Italian NL homepage and subpages (pescetti)
  26. Manually update the downloads from the Japanese NL homepage (nakatamaho)
  27. Manually update the downloads from the Dutch NL homepage (simon.o@brousant.nl)
  28. Manually update the downloads from the Brazilian NL homepage
  29. Manually update the downloads from the Russian NL homepage
  30. Manually update the downloads from the Simplified Chinese NL homepage
  31. Manually update the downloads from the Traditional Chinese NL homepage
  32. After the above have been done, we should pause and confirm that everything is working before going ahead with the announcement.  Let's wait for the Release Manager to signal that we're ready to announce.
  33. Then announcements to ooo-announce, ooo-dev, ooo-users, blog, Twitter, Google+, Twitter, etc.
  34. Seed torrents and update P2P websites:  http://www.openoffice.org/distribution/p2p/

The following is a rough overview which webpage should contain what links. This is to keep the overview at least for the next weeks until all webpages are final and working.

Example URLs:

Webpage

Binaries

SDK

Source

Checksums

ASF mirrors

SF mirrors

MB mirrors

Notes

download/index.html

AOO 3.4.0

–

–

–

–

Yes

–

–

download/other.html

AOO 3.4.0

AOO 3.4.0

–

–

–

Yes

–

–

download/other.html

–

–

AOO 3.4.0

–

Yes

–

–

–

download/checksums.html

–

–

–

AOO 3.4.0

–

–

–

ASF /dist only

legacy/index.html

OOo 3.3.0

–

–

–

–

–

Yes

–

legacy/other.html

OOo 3.3.0

OOo 3.3.0

OOo 3.3.0

–

–

–

Yes

–

legacy/other.html

–

–

–

OOo 3.3.0

–

–

–

OOo /download/md5sums/ only

  • No labels