NeoOffice 3.2.1 Beta Release Tasks

Rebuild all custom NeoOffice code using the existing NeoOffice 3.2.1 Beta development builds. Perform a confirming checkout of the HEAD branch and set build to build with a new version and the NeoOffice trademarked product name.

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=$(PRODUCT_VERSION_BASE).1 Beta
  PRODUCT_DIR_VERSION=$(PRODUCT_VERSION_BASE).1_Beta
  PREVIOUS_PRODUCT_VERSION=$(PRODUCT_VERSION)
  PRODUCT_PATCH_VERSION=Patch 0
  PRODUCT_DIR_PATCH_VERSION=Patch-0
  NEO_TAG:=NeoOffice-3_2_1_Beta
  

• In makefile, reset the patch installer to include the minimum number of files by removing all files added to the build.patch_package_shared make target after the NeoOffice-3_2 tag and changing the following macros to the respective values:

  PRODUCT_COMPONENT_PATCH_MODULES=
  

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

Tag the code in the HEAD branch with the NeoOffice-3_2_1_Beta tag using 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.
• Tag all files in your workspace by invoking cvs tag NeoOffice-3_2_1_Beta.
• If there are any build errors, fix and commit them, retag the changed files by invoking cvs tag -F NeoOffice-3_2_1_Beta, and repeating the step.

Create releasable NeoOffice 3.2.1 Beta build 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-3_2_1_Beta 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_* files. This will force the installer to rebuild all of the NeoOffice custom code without causing any of the OpenOffice.org or ooo-build code to be rebuilt.
• Invoke make all to create the releasable installer and language packs.

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-3.2.1_Beta directory outside of the workspace
• Copy all 34 install/*.dmg files from your releasable build into the empty NeoOffice-3.2.1_Beta directory and chmod 444 *.dmg in that directory

Put the NeoOffice-3.2.1_Beta folder in a new empty directory and create a CD master NeoOffice-3.2.1_Beta.cdr file of the new directory using the following command:

hdiutil create -srcfolder /path/to/new/directory \
-format UDTO -ov -o /path/to/output/NeoOffice-3.2.1_Beta.cdr

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

• 10.5.8
• 10.6.8
• 10.7.0

Upload the 34 NeoOffice NeoOffice-3.2.1_Beta-*.dmg main installer and language pack files to the rsync.neooffice.org server's /neojava/donordownloads directory using the following steps:

• Upload the files to your home directory on the server using the sftp command
• Use the md5 command to verify that the MD5 checksums of the source file and the uploaded file are the same
• Move the file from your home directory to the server's /neojava/donordownloads directory
• Invoke bin/setpermissions.sh so that the files will be readable by all mirrors' webservers

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

Note: I used the following steps to do this:

• Manually edit the /neojava/includes/globals.php page and set the following variables to the following values and delete all but the zero'th element:

$newproductdownloadenabled = true;
$newproductminosxversion = '10.5';
$newproductversion = '3.2.1 Beta';
$newproductfamily[0] = '';
$newoooversion = '3.1.1';
$newpatch = '';

• Manually edit all of the features.php pages in the /neojava directory and update the text in the news banner section.
• Manually edit all of the header.php pages in the /neojava directory and update the text in the news banner section.
• Manually edit all of the index.php pages in the /neojava directory and update the content to highlight any new features.
• After you verify that the changes look correct, invoke the following command to commit your changes: bin/cvsplusperms.sh commit

Verify that patch checking works properly by doing the following steps in a NeoOffice 3.2.1 Beta installation:

• Test as NeoOffice 2.2.6 Patch 5 by opening the installation's Contents/MacOS/versionrc file, changing the UpdateURL line to the following, restarting NeoOffice, and selecting the Help :: Check for Updates menu. The dialog that appears should say that NeoOffice 3.2 is available:

  UpdateURL=http://www-test.neooffice.org/neojava/patchcheck.php?product=NeoOffice%202.2.6&patch=Patch%205&os=${_OS}&arch=${_ARCH}

• Test as NeoOffice 3.0.2 Patch 6 by opening the installation's Contents/MacOS/versionrc file, changing the UpdateURL line to the following, restarting NeoOffice, and selecting the Help :: Check for Updates menu. The dialog that appears should say that NeoOffice 3.2 is available:

  UpdateURL=http://www-test.neooffice.org/neojava/patchcheck.php?product=NeoOffice%203.0.2&patch=Patch%206&os=${_OS}&arch=${_ARCH}

• Test as NeoOffice 3.1.2 Patch 9 by opening the installation's Contents/MacOS/versionrc file, changing the UpdateURL line to the following, restarting NeoOffice, and selecting the Help :: Check for Updates menu. The dialog that appears should say that NeoOffice 3.2 is available:

  UpdateURL=http://www-test.neooffice.org/neojava/patchcheck.php?product=NeoOffice%203.1.2&patch=Patch%209&os=${_OS}&arch=${_ARCH}

• Test as NeoOffice 3.2 Patch 5 by opening the installation's Contents/MacOS/versionrc file, changing the UpdateURL line to the following, restarting NeoOffice, and selecting the Help :: Check for Updates menu. The dialog that appears should say that NeoOffice 3.2 is available:

  UpdateURL=http://www-test.neooffice.org/neojava/patchcheck.php?product=NeoOffice%203.2&patch=Patch%205&os=${_OS}&arch=${_ARCH}

• Test as NeoOffice 3.2.1 Beta by opening the installation's Contents/MacOS/versionrc file, changing the UpdateURL line to the following, restarting NeoOffice, and selecting the Help :: Check for Updates menu. The dialog that appears should say that NeoOffice is up to date.

  UpdateURL=http://www-test.neooffice.org/neojava/patchcheck.php?product=NeoOffice%203.2.1%20Beta&patch=Patch%200&os=${_OS}&arch=${_ARCH}

Make NeoOffice 3.2.1 Beta the current version in the NeoWiki using the following steps:

• In the NeoWiki NeoMainPageVer template, change the NeoOffice version to 3.2 Beta
• In the NeoWiki NeoOfficeWords template, change the NeoOffice release date to 1 August 2011
• In the NeoWiki NeoOfficeWords template, change the NeoOffice release date to 1 août 2011
• In the NeoWiki NeoOfficeWords template, change the NeoOffice release date to 1. August 2011
• In the NeoWiki NeoOfficeWords template, change the NeoOffice release date to 19 agosto 2011
• In the NeoWiki NeoOfficeWords template, change the NeoOffice release date to el 19 de agosto de 2011
• In the NeoWiki NeoOfficeWords template, change the NeoOffice release date to 19 augustus 2011

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 "3.2.1 Beta"
• Set "Closed in Version" field to "3.2.1 Beta"

Close any bugs with a status of "Assigned" or "Reopened" and resolution of "Fixed" by setting the following field values:

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

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 last year using the following steps:

• Login to PayPal, click on the History tab, click on Download My History link, select Custom Date Range, enter the date for a year ago in "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.