NeoOffice 3.0 Release Tasks

Verify that OpenOffice.org does not have a newer tag for version 3.0.x than the OOO300_m14 tag.

Verify that ooo-build does not have a newer tag for version 3.0.x than the OOO_BUILD_3_0_1 branch.

Verify that Novell's patched odf-converter does not have a newer version than 2.5-2 in Novell's odf-converter source repository.

Rebuild all custom NeoOffice code using the existing NeoOffice 3.0 Early Access 2 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_FAMILY=3.0
  PRODUCT_VERSION=3.0
  PREVIOUS_PRODUCT_VERSION=$(PRODUCT_VERSION)
  PRODUCT_DIR_VERSION=3.0
  PRODUCT_PATCH_VERSION=Patch 0
  PRODUCT_DIR_PATCH_VERSION=Patch-0
  NEO_TAG:=-rNeoOffice-3_0
  

• In makefile, reset the patch installer to include the minimum number of files by removing all files add to the build.patch_package_shared make target after the NeoOffice-3_0_Early_Access 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.

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
for i in `find . -name "*.dylib*" -o -name "*.bin"`; 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.

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

Create releasable NeoOffice 3.0 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_0 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_* and build.odf-converter* 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 all to create the releasable installer and language packs.

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

Put the NeoOffice-3.0 folder in a new empty directory and create a CD master NeoOffice-3.0.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.0.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.

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

• 10.4.11
• 10.5.6

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

• 10.4.11
• 10.5.6

Verify that the releasable installer does not allow installation on PowerPC for the following Mac OS X versions:

• 10.3.9

Update all NeoOffice and version names, file URLs, and patch version names in all of the files in the www-test.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:

$earlyaccessdownloadenabled = true;
$earlyaccessredirectenabled = false;
$earlyaccessfreeproduct = 'NeoOffice 3.0';
$earlyaccessproductversion = '3.0';
$earlyaccessproductfamily[0] = '';
$earlyaccesspatch = 'Patch 0';

• Manually edit all of the header.html pages in the /neojava directory and put the NeoOffice 3.0 announcement within the new banner's "if ($earlyaccessdownloadenabled)" section.
• Manually edit all of the earlyaccess.php pages in the /neojava directory and add the previous Program to the list past Programs wherever they are listed.
• Manually edit all of the earlyaccess.php pages in the /neojava directory and update the Program start and end dates wherever they are listed.
• Manually edit all of the earlyaccessfeatures.php pages in the /neojava directory and add any new or missing features compared to the matching OpenOffice.org version.
• Manually edit the /neojava/donations/config.php file and set the DONATIONSDOWNLOADCOOKIEKEY and DONATIONSDOWNLOADCOOKIEVALUE defines to values that have not been used in past Programs.
• After you verify that the changes look correct, invoke the following command to commit your changes: cvs commit ; chmod -Rf ug+rw .[ch]* *

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 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 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.

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.0 EA"
• Set "Closed in Version" field to "3.0 EA"

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

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