NeoOffice 2.2.3 Release Tasks

Verify that ooo-build does not have a newer tag than the OOO_BUILD_2_2_1 tag.

Verify that odf-converter does not have a newer tag than the Rlease-1.1 tag.

Rebuild all custom NeoOffice and RetroOffice code using the existing NeoOffice 2.2.2 Patch 11 test patch builds. Perform a confirming checkout of the HEAD branch and set build to build with a new version and NeoOffice and RetroOffice trademarked product names.

This includes the following steps:

• Do a cvs update -Ad to ensure that you have the latest code in your workspace, verify that none of the files are marked as updated, patched, modified, or have conflicts, and verify that the latest code actually builds through the installer.
• Copy custom.neo.mk file to custom.mk so that the clean checkout will build with the trademarked product names.

• In makefile, change the following macros to the respective values:

  PRODUCT_VERSION=2.2.3
  PRODUCT_DIR_VERSION=2.2.3
  X11_PRODUCT_VERSION=2.2.3
  X11_PRODUCT_DIR_VERSION=2.2.3
  PRODUCT_PATCH_VERSION=Patch 0
  PRODUCT_DIR_PATCH_VERSION=Patch-0
  X11_PRODUCT_PATCH_VERSION=Patch 0
  X11_PRODUCT_DIR_PATCH_VERSION=Patch-0
  NEO_TAG:=-rNeoOffice-2_2_3
  X11_NEO_TAG:=-rRetroOffice-2_2_3
  

• Delete all build.neo_* files so that all custom NeoOffice and RetroOffice code will be rebuilt.
• Commit makefile changes and invoke make build.patch_package build.patch_package_X11 to rebuild all applicable code and installers.

Verify that none of the NeoOffice Intel build's executables or libraries link to any X11 libraries.

Note: to do this task, install your latest NeoOffice build and, in a terminal, execute the following commands:

sh
cd /Applications/NeoOffice.app/Contents/MacOS
for i in `find . -type f`; do echo $i ; otool -L $i 2>&1 | grep X11; done

If none of the binaries link to any X11 libraries, the above commands will only print a list of files. However, if you see any lines that look similar to the following, the file listed just before this type of line is linked to an X11 library and this must be correct before the NeoOffice binaries can be released.

/usr/X11R6/lib/libX11.6.dylib (compatibility version 6.2.0, current version 6.2.0)

Verify that none of the NeoOffice PowerPC build's executables or libraries link to any X11 libraries.

Note: Use the same steps as used for the matching Intel task.

Modify and test bin/installutils script to treat all NeoOffice 2.2.x installations as a match.

In this release, language pack resource files are compatible so we want to preserve them in they exist.

Note: I tested this code by building the installer, language packs, and patch installer and then doing the following steps:

• Install the patch installer and verify that it does not upgrade my NeoOffice 2.2.2 Early Access installation but does upgrade my NeoOffice 2.2.2 installation.
• Install a NeoOffice 2.2.3 language pack, change my machine's preferred language to match the installed language pack, run NeoOffice 2.2.3, and verify that the menus are not in English.
• With the same preferred language set in the previous step, install NeoOffice 2.2.3, and verify that the menus are still not in English.

Tag the code in the HEAD branch with the NeoOffice-2_2_3 and RetroOffice-2_2_3 tags using the following:

• Do a cvs update -Ad to ensure that you have the latest code in your workspace, verify that none of the files are marked as updated, patched, modified, or have conflicts, and verify that the latest code actually builds through the installer.
• In the makefile, set the NEO_TAG macro to NEO_TAG:=-rNeoOffice-2_2_3 and X11_NEO_TAG macro to X11_NEO_TAG:=-rRetroOffice-2_2_3 and commit the makefile.
• Tag all files in your workspace by invoking cvs tag NeoOffice-2_2_3 ; cvs tag RetroOffice-2_2_3.
• Verify that the installer still builds by deleting the build.source_zip* files and invoking make NOLANGPACKS=true.
• If there are any build errors, fix and commit them, retag the changed files by invoking cvs tag -F NeoOffice-2_2_3 ; cvs tag -F RetroOffice-2_2_3, and repeating the previous two steps.

Create releasable NeoOffice 2.2.3 and RetroOffice 2.2.3 builds for Intel.

Note: the following steps are overkill, but they ensure that all recent changes to the NeoOffice custom code has been built:

• Do a cvs update -d -rNeoOffice-2_2_3 and verify that none of the files are marked as updated, patched, modified, or have conflicts. If any such errors appear, the previous task (tagging of the workspace) has not been done properly and it needs to done properly before you can proceed with this task.
• Do a cvs update -Ad so that you can do bug fixing and release patches after you create your releasable build
• Delete all build.neo_*, build.odf-converter*, and build.source_zip* files. This will force the installer to rebuild the odf-converter code and all of the NeoOffice custom code without causing any of the OpenOffice.org or ooo-build code to be rebuilt.
• Invoke make build.patch_package build.patch_package_X11 to create the releasable installer, language packs, and patch installers.

Create releasable NeoOffice 2.2.3 and RetroOffice 2.2.3 builds for PowerPC.

Note: Use the same steps as used for the matching Intel task.

Create backup copy of releasable Intel binaries and upload them to staging server.

The following steps are the steps that I used to create my backup copy:

• Create an empty NeoOffice-2.2.3 directory outside of the workspace
• Copy all 58 install/*.dmg files from your releasable build into the empty NeoOffice-2.2.3 directory and chmod 444 *.dmg in that directory
• Copy all patch_install/*.dmg files from your releasable build into the empty NeoOffice-2.2.3 directory and chmod 444 *.dmg in that directory

sftp all 58 files up to staging server and chmod 444 *.dmg all of the files on the staging server.

sftp the patch installer file up to staging server and chmod 444 *.dmg all of the files on the staging server.

diff the md5 *Intel.dmg | sort' output of the files on the server and in local NeoOffice-2.2.3 directory.

Repeat the above steps using RetroOffice-2.2.3 instead of NeoOffice-2.2.3 and install_X11/*.dmg instead of install/*.dmg.

Put the NeoOffice-2.2.3 and RetroOffice-2.2.3 folders in a new empty directory and create a CD master NeoRetroOffice-2.2.3.cdr file of the new directory using the following command:

hdiutil create -srcfolder /path/to/new/directory \
-format UDTO -ov -o /path/to/output/NeoRetroOffice-2.2.3.cdr

Create backup copy of releasable PowerPC binaries and upload them to staging server.

Note: Use the same steps as used for the matching Intel task (except diff using md5 *PowerPC.dmg | sort'.

Verify that the releasable installers and one or more language packs install and run on Intel for the following Mac OS X versions:

• 10.4.10
• 10.5.0 developer seed 9A559

Verify that the releasable installers and one or more language packs install and run on PowerPC for the following Mac OS X versions:

• 10.3.9
• 10.4.10
• 10.5.0 developer seed 9A559

Make room for the new NeoOffice binaries by removing the NeoOffice 2.2.2 binaries from the www.planamesa.org mirror site.

Note: the following steps were used to complete this task:

• Login to the www.neooffice.org server, cd to the its webroot directory, and invoke the following command: cvs update -Ad ; chmod -Rf ug+rw .htaccess *.
• Comment out the www.planamesa.org server from the /neojava/mirrors.php file in the www.neooffice.org website's /neojava/mirrors.php file and invoke the following command to commit your changes: cvs commit ; chmod -Rf ug+rw .htaccess *.
• Delete all NeoOffice-2.2.2-*.dmg files from the www.planamesa.org server.

Create a tag for the www.neooffice.org website to avoid modifying production web pages while we modify the web pages in the test website. Steps:

• Construct a local checkout of the website: cvs co www_htdocs
• cd into the checkout directory and tag the checkout by invoking the following command: cvs tag NeoRetroOffice-2_2_2
• Login to the www.neooffice.org server, cd to the its webroot directory, and set the tag by invoking the following command: cvs update -d -rNeoRetroOffice-2_2_2 ; chmod -Rf ug+rw .htaccess *

Update all NeoOffice and RetroOffice version names, file URLs, and patch version in all of the files in the www-test.neooffice.org server's neojava and retro directories.

Note: I used the following steps to do this:

• Update the version name, patch version, and file URLs by executing the following commands in the / directory of the web pages:

sh
for i in `find neojava retro -name "*.php" -o -name "header.html" | grep -v 'index\.php'`; do
sed 's#2\.2\.2#2.2.3#g' $i | \
sed 's#Patch 10#Patch 0#g' | \
sed 's#Patch-10#Patch-0#g' > $i.tmp

mv $i.tmp $i
done

• Manually edit the /neojava/globals.php page and set the following variables to the following values:

$currentproductfamily[0] = 'NeoOffice 2.2.1';
$currentproductfamily[1] = 'NeoOffice 2.2.2';

• Manually edit the /retro/globals.php page and set the following variables to the following values:

$currentproductfamily[0] = 'RetroOffice 2.2.1';
$currentproductfamily[1] = 'RetroOffice 2.2.2';

• Manually edit all of the patch.php pages and replace 2.2.3 with 2.2.2 in the 5th and 6th occurrences from the end of the file.
• Manually edit the news banner text in all of the header.html pages and insert a line that says "NeoOffice 2.2.2 users: Upgrade to NeoOffice 2.2.3 by downloading the latest patch".
• Manually edit all of the index.php pages, copy the "27 August 2007" line in the "News" section to a new line above it, change in the new line any occurrences of "NeoOffice 2.2.2" to "NeoOffice 2.2.3", any occurrences of "RetroOffice 2.2.2" to "RetroOffice 2.2.3", and the date to "10 October 2007", and delete the sentence with the download link in the "27 August 2007" line.
• After you verify the that changes look correct, invoke the following command to commit your changes: cvs commit ; chmod -Rf ug+rw .htaccess *

Update the 116 NeoOffice 2.2.3 file sizes in all of the *download.php files in the /neojava directory of the www-test.neooffice.org server's web pages.

Note: I used the following steps to do this:

• Login to the www-test.neooffice.org server, cd to the its webroot directory, and invoke the following command: cvs update -Ad ; chmod -Rf ug+rw .htaccess *
• Get a file containing the new release's file names and the matching file sizes from the NeoOffice 2.2.2 release by executing the following command:

ls -l /directory/NeoOffice-2.2.2/binaries/NeoOffice-2.2.2-*.dmg | \
awk '{print $9 " " $5}' | \
sed 's#^.*NeoOffice-2.2.2#NeoOffice-2.2.3#' | \
sort > /path/to/a/new/file

• Get a file containing the new release's file names and the matching file sizes by executing the following commands:

ls -l /directory/NeoOffice-2.2.3/binaries/NeoOffice-2.2.3-*.dmg | \
awk '{print $9 " " $5}' | \
sort > /path/to/a/new/file

• Create a chained list of sed commands by executing the following command:

join /file/from/first/step /file/from/second/step | \
sed 's#^.*dmg ##' | \
sed 's# #\##' | \
sed 's#^#sed "s\##' | \
sed 's#$#\#g" | \\#' > /path/to/a/new/file

• Manually edit the file created in the last step and insert the following lines before the first sed command:

for i in `find . -name "*download.php"`; do
cat $i | \

• Manually edit the same file and insert the following lines after the last sed command:

cat > $i.tmp
mv $i.tmp $i
done

• cd to the /neojava directory and execute the following command to update all of the file sizes:

sh /path/to/file/edited/in/last/step

• After you verify the that changes look correct, invoke the following command to commit your changes: cvs commit ; chmod -Rf ug+rw .htaccess *

Update the 116 RetroOffice 2.2.3 file sizes in all of the *download.php files in the /retro directory of the www-test.neooffice.org server's web pages.

Note: I used the following steps to do this:

• Login to the www-test.neooffice.org server, cd to the its webroot directory, and invoke the following command: cvs update -Ad ; chmod -Rf ug+rw .htaccess *
• Get a file containing the new release's file names and the matching file sizes from the RetroOffice 2.2.2 release by executing the following command:

ls -l /directory/RetroOffice-2.2.3/binaries/RetroOffice-2.2.2-*.dmg | \
awk '{print $9 " " $5}' | \
sed 's#^.*RetroOffice-2.2.2#RetroOffice-2.2.3#' | \
sort > /path/to/a/new/file

• Get a file containing the new release's file names and the matching file sizes by executing the following commands:

ls -l /directory/RetroOffice-2.2.3/binaries/RetroOffice-2.2.3-*.dmg | \
awk '{print $9 " " $5}' | \
sort > /path/to/a/new/file

• Create a chained list of sed commands by executing the following command:

join /file/from/first/step /file/from/second/step | \
sed 's#^.*dmg ##' | \
sed 's# #\##' | \
sed 's#^#sed "s\##' | \
sed 's#$#\#g" | \\#' > /path/to/a/new/file

• Manually edit the file created in the last step and insert the following lines before the first sed command:

for i in `find . -name "*download.php"`; do
cat $i | \

• Manually edit the same file and insert the following lines after the last sed command:

cat > $i.tmp
mv $i.tmp $i
done

• cd to the /retro directory and execute the following command to update all of the file sizes:

sh /path/to/file/edited/in/last/step

• After you verify the that changes look correct, invoke the following command to commit your changes: cvs commit ; chmod -Rf ug+rw .htaccess *

Update the 2 NeoOffice 2.2.3 patch file sizes in all of the *patch.php files in the /neojava directory of the www-test.neooffice.org server's web pages.

Note: I used the following steps to do this:

• Login to the www-test.neooffice.org server, cd to the its webroot directory, and invoke the following command: cvs update -Ad ; chmod -Rf ug+rw .htaccess *
• cd to the /neojava directory and execute the following command to update all of the file sizes:

sh
oldpowerpcpatchsize="<fill in number of bytes>"
oldintelpatchsize="<fill in number of bytes>"
newpowerpcpatchsize="<fill in number of bytes>"
newintelpatchsize="<fill in number of bytes>"
for i in `find . -name "*patch.php"`; do \
sed "s#$oldpowerpcpatchsize#$newpowerpcpatchsize#g" $i | \
sed "s#$oldintelpatchsize#$newintelpatchsize#g" > $i.tmp
mv $i.tmp $i
done

• After you verify the that changes look correct, invoke the following command to commit your changes: cvs commit ; chmod -Rf ug+rw .htaccess *

Update the 2 RetroOffice 2.2.3 patch file sizes in all of the *patch.php files in the /retro directory of the www-test.neooffice.org server's web pages.

Note: I used the following steps to do this:

• Login to the www-test.neooffice.org server, cd to the its webroot directory, and invoke the following command: cvs update -Ad ; chmod -Rf ug+rw .htaccess *
• cd to the /retro directory and execute the following command to update all of the file sizes:

sh
oldpowerpcpatchsize="<fill in number of bytes>"
oldintelpatchsize="<fill in number of bytes>"
newpowerpcpatchsize="<fill in number of bytes>"
newintelpatchsize="<fill in number of bytes>"
for i in `find . -name "*patch.php"`; do \
sed "s#$oldpowerpcpatchsize#$newpowerpcpatchsize#g" $i | \
sed "s#$oldintelpatchsize#$newintelpatchsize#g" > $i.tmp
mv $i.tmp $i
done

• After you verify the that changes look correct, invoke the following command to commit your changes: cvs commit ; chmod -Rf ug+rw .htaccess *

Enable the BitTorrent links using the following steps:

• Obtain the 2 NeoOffice-2.2.3-*.torrent files from the mirrors.freesmug.org mirror maintainer and cvs add these 2 files in the www-test.neooffice.org website's /neojava/downloads directory.
• After you verify the that changes look correct, invoke the following command to commit your changes: cvs commit ; chmod -Rf ug+rw .htaccess *

Obtain each localized version of the NeoOffice 2.2.3 press release in HTML format, save them in the www-test.neooffice.org website's /neojava/press_releases directory using the following naming format so that the webserver's language detection will serve the closest matching file, cvs add the files, and invoke the following command to commit your changes: cvs commit ; chmod -Rf ug+rw .htaccess *:

• English - Save as two files: NeoOffice_2.2.3.html.en and NeoOffice_2.2.3.html.html
• Other languages - Save using the format NeoOffice_2.2.3.html.<two-digit-language-code> replacing <two-digit-language-code> with the standard language code (e.g. de for German, fr for French, etc.

Close all bugs with a status of "Resolved" by setting the following field values:

• Set "Status" field to "Closed"
• Set "Resolution" field to "Fixed"
• Set "Target Version" field to "2.2.3"
• Set "Closed in Version" field to "2.2.3"

Close any bugs with a status of "Assigned" and resolution of "Fixed" (bugs fixed in the release build after the final Early Access patch) by setting the following field values:

• Set "Status" field to "Closed"
• Set "Resolution" field to "Fixed"
• Set "Target Version" field to "2.2.3"
• Set "Closed in Version" field to "2.2.3"

Synchronize the donation's database to PayPal's database to ensure that none of the donors' transactions are missing and to pick up any e-mail address changes made by donors during the Early Access period using the following steps:

• Login to PayPal, click on the History tab, click on Download My History link, select Custom Date Range, enter the day before the start of the Early Access period as the "From" date and the current date as the "To" date, and "Comma Delimited - All Activity" as the "File Types to Download".
• It will take some time for PayPal to prepare the file. Once the file is ready, download it and use sftp to copy it to the www.neooffice.org server. Note: be sure to delete your local copy.
• Once the history file is on the www.neooffice.org server, login to the server, cd to the /donationsadmin directory, and execute the following command to import the history file:

  sh
  ./import_paypal_transaction_history.php /path/to/history/file 2>/path/to/error/file
  

• Inspect the entries in the error file created in the previous command and verify that none of the rejected lines from the file are donor transactions.