Space: Apache OpenOffice Community 
(https://cwiki.apache.org/confluence/display/OOOUSERS)
Page: AOO 3.4 Distribution Tasks 
(https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Distribution+Tasks)


Edited by Kay Schenk:
---------------------------------------------------------------------
The following tasks need to be done to support the distribution of AOO 3.4 once 
its release is approved.
# 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.
# Submit the AOO URL's and SHA256 hashes to Symantec to "whitelist" us in their 
anti-virus:  [https://submit.symantec.com/whitelist/isv/new/]
# Disable the downloads directly from www.openoffice.org.  Instead have 
the download link go to download/index.html (*robweir*, done)
# Make a copy of the the older MirrorBrain-enabled download/index.html and 
download/other.html pages.  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*, in progress)
# Update download/index.html and 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. (*kay*, in progress)
# Location for source artifact linked from other.html?
# Update install guide if needed. (*kay*, in progress)
# 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 the wave*)
# Update branding of download/index.html and download/other.html to "Apache 
OpenOffice" rather than OpenOffice.org
# Check and update license (and other) links on the "new" download page.
# Add text to these pages (or a new page linked to from download/index.html and 
other.html) explaining how to verify the hashes and detached digital 
signatures.  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, not to the mirrors.
# Manually update downloads from the Mac porting page and subpages:  
[http://www.openoffice.org/porting/mac/] (*marcus*)
# Manually update the downloads from the Arabic NL homepage
# Manually update the downloads from the Czech NL homepage
# Manually update the downloads from the German NL homepage
# Manually update the downloads from the Spanish NL homepage
# Manually update the downloads from the French NL homepage
# Manually update the downloads from the Hungarian NL homepage
# Manually update the downloads from the Galacian NL homepage
# Manually update the downloads from the Italian NL homepage and subpages 
(*pescetti*)
# Manually update the downloads from the Japanese NL homepage
# Manually update the downloads from the Dutch NL homepage
# Manually update the downloads from the Brazilian NL homepage
# Manually update the downloads from the Russian NL homepage
# Manually update the downloads from the Simplified Chinese NL homepage
# Manually update the downloads from the Traditional Chinese NL homepage
# 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.
# Then announcements to ooo-announce, ooo-dev, ooo-users, blog, Twitter, 
Google+, Twitter, etc.
# Seed torrents and update P2P websites:  
[http://www.openoffice.org/distribution/p2p/]

Change your notification preferences: 
https://cwiki.apache.org/confluence/users/viewnotifications.action    

Reply via email to