NeoOffice 3.0.1 Release Tasks

From NeoWiki

Revision as of 01:07, 17 October 2009 by ( | contribs)
Jump to: navigation, search

This page is an attempt to document all of the tasks required to release NeoOffice 3.0.1. This page is by no means comprehensive, but hopefully as we work through the release process, we will leave behind enough details to make future releases simpler and less error prone.

Here is what the colors mean:

Not yet assigned
Assigned but not yet due

Contents

Builds

In this release, while we are not making changes to NeoOffice's underlying OpenOffice.org code or adding any new application or toolbar icons, the size of the last NeoOffice 3.0.1 Early Access test patch too large for a new release so no upgrade patch will be released.

TaskDate CompletedAssignedStatus

Rebuild all custom NeoOffice code using the existing NeoOffice 3.0.1 Early Access development builds. Perform a confirming checkout of the HEAD branch and set build to build with a new version and the NeoOffice 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=3.0.1
    PRODUCT_DIR_VERSION=3.0.1
    PREVIOUS_PRODUCT_VERSION=$(PRODUCT_VERSION)
    PRODUCT_PATCH_VERSION=Patch 0
    PRODUCT_DIR_PATCH_VERSION=Patch-0
    NEO_TAG:=-rNeoOffice-3_0_1
    
  • 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.
10/14/2009plubyDone

Rebuild all custom NeoOffice code using the existing NeoOffice 2.2.6 Early Access development builds. Perform a confirming checkout of the NeoOffice-2_2_6_branch branch and set build to build with a new version and the NeoOffice trademarked product names.

This includes the following steps:

  • Do a cvs update -rNeoOffice-2_2_6_branch branch -d 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.6
    PRODUCT_DIR_VERSION=2.2.6
    PREVIOUS_PRODUCT_VERSION=$(PRODUCT_VERSION)
    X11_PRODUCT_VERSION=2.2.6
    X11_PRODUCT_DIR_VERSION=2.2.6
    X11_PREVIOUS_PRODUCT_VERSION=$(X11_PRODUCT_VERSION)
    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_6
    X11_NEO_TAG:=
    
  • 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.
10/14/2009plubyDone

Verify that none of the NeoOffice 3.0.1 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 . -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)
10/15/2009plubyDone

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

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

10/15/2009plubyDone

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

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

10/15/2009plubyDone

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

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

10/15/2009plubyDone

Tag the code in the HEAD branch with the NeoOffice-3_0_1 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_1.
  • If there are any build errors, fix and commit them, retag the changed files by invoking cvs tag -F NeoOffice-3_0_1, and repeating the step.
10/14/2009plubyDone

Tag the code in the NeoOffice-2_2_6_branch branch with the NeoOffice-2_2_6 tag using the following:

  • Do a cvs update -rNeoOffice-2_2_6_branch -d 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-2_2_6.
  • If there are any build errors, fix and commit them, retag the changed files by invoking cvs tag -F NeoOffice-2_2_6, and repeating the step.
10/14/2009plubyDone

Create releasable NeoOffice 3.0.1 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_1 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 the build.package file. This will force the installer and language packs to be rebuilt without causing any of the code to be rebuilt.
  • Invoke make all to create the releasable installer and language packs.
10/15/2009plubyDone

Create releasable NeoOffice 3.0.1 build for PowerPC.

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

10/15/2009plubyDone

Create releasable NeoOffice 2.2.6 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 -rNeoOffice-2_2_6 -d 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 -rNeoOffice-2_2_6_branch -d so that you can do bug fixing and release patches after you create your releasable build
  • Delete the build.package file. This will force the installer and language packs to be rebuilt without causing any of the code to be rebuilt.
  • Invoke make all to create the releasable installer and language packs.
10/15/2009plubyDone

Create releasable NeoOffice 2.2.6 build for PowerPC.

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

10/15/2009plubyDone

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

Put the NeoOffice-3.0.1 folder in a new empty directory and create a CD master NeoOffice-3.0.1.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.1.cdr
10/15/2009plubyDone

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

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

10/15/2009plubyDone

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

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

10/15/2009plubyDone

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

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

10/15/2009plubyDone

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

  • 10.4.11
  • 10.5.8
  • 10.6.1
10/15/2009plubyDone

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

  • 10.4.11
  • 10.5.8
10/15/2009plubyDone

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

  • 10.4.11
  • 10.5.8
  • 10.6 developer seed build 10A432
10/15/2009plubyDone

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

  • 10.3.9
  • 10.4.11
  • 10.5.8
10/15/2009plubyDone

Mirrors for Early Access Program Release

NeoOffice's rsync server is hosted on rsync.neooffice.org and our volunteer mirrors obtain the NeoOffice binaries by nightly runs of the following command on their mirrors:

rsync --archive --delete rsync://rsync.neooffice.org/neojavadownloads/ \
/path/to/NeoOffice/mirror/directory

Note that the NeoOffice Early Access Program main installer binaries are only mirrored on neooffice.org servers so using the above command will only copy the language pack installers until near the end of the current NeoOffice Early Access Program on 27 October 2009.

TaskDate CompletedAssignedStatus

Upload the 2 main installer NeoOffice-3.0.1-*.dmg files to the joe.neooffice.org server's /neojava/earlyaccessdownloads 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
  • Invoke cd ~ ; chmod 444 NeoOffice-3.0.1-*.dmg so that the files will be readable by all mirrors' webservers
  • Move the file from your home directory to the server's /neojava/earlyaccessdownloads directory
pluby

Upload the 116 NeoOffice language pack installer NeoOffice-3.0.1-Language_Pack_*.dmg files to the joe.neooffice.org server's /neojava/downloads 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
  • Invoke cd ~ ; chmod 444 NeoOffice-3.0.1-Language_Pack_*.dmg so that the files will be readable by all mirrors' webservers
  • Move the file from your home directory to the server's /neojava/downloads directory
10/16/2009plubyDone

Upload the 2 main installer NeoOffice-2.2.6-*.dmg files to the joe.neooffice.org server's /neojava/earlyaccessdownloads 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
  • Invoke cd ~ ; chmod 444 NeoOffice-2.2.6-*.dmg so that the files will be readable by all mirrors' webservers
  • Move the file from your home directory to the server's /neojava/earlyaccessdownloads directory
pluby

Upload the 112 NeoOffice language pack installer NeoOffice-2.2.6-Language_Pack_*.dmg files to the joe.neooffice.org server's /neojava/downloads 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
  • Invoke cd ~ ; chmod 444 NeoOffice-2.2.6-Language_Pack_*.dmg so that the files will be readable by all mirrors' webservers
  • Move the file from your home directory to the server's /neojava/downloads directory
10/16/2009plubyDone

Mirrors

NeoOffice's rsync server is hosted on rsync.neooffice.org and our volunteer mirrors obtain the NeoOffice binaries by nightly runs of the following command on their mirrors:

rsync --archive --delete rsync://rsync.neooffice.org/neojavadownloads/ \
/path/to/NeoOffice/mirror/directory

Note that since we already mirrored the language pack installers, we only need to mirror the main installers.

TaskDate CompletedAssignedStatus

Copy the 2 main installer NeoOffice-3.0.1-*.dmg files to the joe.neooffice.org server's /neojava/downloads directory using the following steps:

  • Copy the files to your home directory from the server's /neojava/earlyaccessdownloads directory
  • Use the md5 command to verify that the MD5 checksums of the source file and the copied file are the same
  • Invoke cd ~ ; chmod 444 NeoOffice-3.0.1-*.dmg so that the files will be readable by all mirrors' webservers
  • Move the file from your home directory to the server's /neojava/downloads directory
pluby

Copy the 2 main installer NeoOffice-2.2.6-*.dmg files to the joe.neooffice.org server's /neojava/downloads directory using the following steps:

  • Copy the files to your home directory from the server's /neojava/earlyaccessdownloads directory
  • Use the md5 command to verify that the MD5 checksums of the source file and the copied file are the same
  • Invoke cd ~ ; chmod 444 NeoOffice-2.2.6-*.dmg so that the files will be readable by all mirrors' webservers
  • Move the file from your home directory to the server's /neojava/downloads directory
pluby

Website for Early Access Program Release

TaskDate CompletedAssignedStatus
Tag the www.neooffice.org website to avoid modifying production web pages while we modify the web pages in the test website by logging into the www.neooffice.org server, cd to the its webroot directory, and set the tag by invoking the following commands: sudo chmod -Rf ug+rw . ; cvs tag NeoOffice-3_0_1_Early_Access ; cvs update -rNeoOffice-3_0_1_Early_Access -d ; sudo chmod -Rf g-w,o-rwx . 10/16/2009plubyDone

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:
  • $earlyaccessdownloadenabled = true;
    $earlyaccessredirectenabled = false;
    $earlyaccessfreeproduct = 'NeoOffice 3.0.1';
    $earlyaccessproductversion = '3.0.1';
    $earlyaccessproductfamily[0] = '3.0.1 Early Access';
    $earlyaccesspatch = '';
    $oldearlyaccessproductversion = '2.2.6';
    $oldearlyaccessproductfamily[0] = '2.2.6 Early Access';
    
  • After you verify that the changes look correct, invoke the following command to commit your changes: sudo chmod -Rf ug+rw . ; cvs commit ; sudo chmod -Rf g-w,o-rwx .
10/16/2009plubyDone
Update the NeoOffice 3.0.1 and NeoOffice 2.2.6 main installer and language pack file sizes and set the 4 patch file sizes to 0 in the /neojava/includes/globals/earlyaccessfilesizes.php file and if the changes look correct, invoke the following command to commit your changes: sudo chmod -Rf ug+rw . ; cvs commit ; sudo chmod -Rf g-w,o-rwx . 10/16/2009plubyDone

Website

TaskDate CompletedAssignedStatus
Tag the www.neooffice.org website to avoid modifying production web pages while we modify the web pages in the test website by logging into the www.neooffice.org server, cd to the its webroot directory, and set the tag by invoking the following commands: sudo chmod -Rf ug+rw . ; cvs tag NeoOffice-3_0_1 ; cvs update -rNeoOffice-3_0_1 -d ; sudo chmod -Rf g-w,o-rwx . pluby

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:
  • $earlyaccessdownloadenabled = true;
    $earlyaccessredirectenabled = false;
    $earlyaccessfreeproduct = 'NeoOffice 3.0.1';
    $earlyaccessproductversion = '3.0.1 Early Access';
    $earlyaccessproductfamily[0] = '';
    $earlyaccesspatch = 'Patch 0';
    $oldearlyaccessproductversion = '2.2.6 Early Access';
    $oldearlyaccessproductfamily[0] = '';
    
  • Manually edit all of the header.html pages in the /neojava directory and put the NeoOffice 3.0.1 Early Access 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 Early Access Program to the list past Early Access Programs wherever they are listed.
  • Manually edit all of the earlyaccess.php pages in the /neojava directory and update the Early Access 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 Early Access Programs.
  • After you verify that the changes look correct, invoke the following command to commit your changes: cvs commit
pluby
Update the 118 NeoOffice 3.0.1 Early Access and 114 NeoOffice 2.2.6 Early Access file sizes in all of the /neojava/includes/globals/earlyaccesfilesizes.php file and if the changes look correct, invoke the following command to commit your changes: cvs commit pluby
Manually edit the mirror_htdocs CVS module's /neojava/earlyaccessdownloads/.htaccess, update any lines to match the changes made in the www_htdocs CVS module's /neojava/donations/config.php file, and if the changes look correct, invoke the following command to commit your changes: cvs commit. Then, propagate the change by logging into each of the servers listed in the www_htdocs CVS module's /neojava/includes/earlyaccessmirrors.php file and invoking the following command: cvs commit pluby
Update the name and start and end dates for the current Early Access Program membership and subscription categories in the Early Access Program database by logging into the the www.neooffice.org server and using the server's /neojava/donationsadmin/manage_categories.php program to update the names and start and end dates for the current Early Access Program membership and subscription categories. Note that the start date should overlap slightly with the end date of the last Early Access Program to ensure that no donations get missed. pluby
Prepare the NeoOffice_3.0.1_Early_Access.html press release file, save it in the www-test-primary.neooffice.org website's /press_releases directory using the following naming format, cvs add the file, and invoke the following command to commit the new file: cvs commit 09/14/2009narfDone

Release for Early Access Program

Generally, we release the new version to Early Access Program members through the Early Access Program download site a few days before we release the new version to the general public. In this release, we plan to make the release available on the Early Access Program download site in the afternoon on 18 October 2009 in California.

TaskDate CompletedAssignedStatus

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.
pluby
Verify that all mirrors listed for the NeoOffice 3.0.1 and NeoOffice 2.2.6 main installer and language pack links work in the www-test.neooffice.org website's Early Access Program download pages. If any do not work, comment them out in the /neojava/includes/earlyaccessmirrors.php file (for the main installer) and in the neojava/includes/mirror.php (for the language packs) and invoke the following command: sudo chmod -Rf ug+rw . ; cvs commit ; sudo chmod -Rf g-w,o-rwx .. pluby
Replace the NeoOffice 3.0.1 Early Access MD5 checksums with the NeoOffice 3.0.1 MD5 checksums. pluby
Replace the NeoOffice 2.2.6 Early Access MD5 checksums with the NeoOffice 2.2.6 MD5 checksums. pluby
Add "3.0.1" and "2.2.6" as versions in Bugzilla. 10/16/2009plubyDone
Make the NeoOffice 3.0.1 and NeoOffice 2.2.6 binaries downloadable from the www.neooffice.org website's Early Access Program download pages by updating the www.neooffice.org website's pages to match what is in the www-test.neooffice.org website's pages. Login into the www.neooffice.org servers, cd to the its webroot directory, and invoke the following command: sudo chmod -Rf ug+rw . ; cvs update -Ad ; sudo chmod -Rf g-w,o-rwx .. pluby

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.1"
  • Set "Closed in Version" field to "3.0.1"
narf

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.0.1"
  • Set "Closed in Version" field to "3.0.1"
narf
Delete the 2 obsolete NeoOffice-3.0.1-Early_Access-*.dmg main installer files from the /neojava/earlyaccessdownloads directory on all of the mirrors listed in the joe.neooffice.org server's /neojava/includes/earlyaccessmirrors.php file. pluby
Delete the 2 obsolete NeoOffice-2.2.6-Early_Access-*.dmg main installer files from the /neojava/earlyaccessdownloads directory on all of the mirrors listed in the joe.neooffice.org server's /neojava/includes/earlyaccessmirrors.php file. pluby
Delete the 116 obsolete NeoOffice-3.0.1_Early_Access-Language_Pack_*.dmg language pack installer files from the rsync.neooffice.org server's /neojava/downloads directory. pluby
Delete the 112 obsolete NeoOffice-2.2.6_Early_Access-Language_Pack_*.dmg language pack installer files from the rsync.neooffice.org server's /neojava/downloads directory. pluby
Delete the 2 obsolete NeoOffice-3.0.1_Early_Access-Patch-*.dmg patch installer files from the rsync.neooffice.org server's /neojava/downloads/patches directory. pluby
Delete the 2 obsolete NeoOffice-2.2.6_Early_Access-Patch-*.dmg patch installer files from the rsync.neooffice.org server's /neojava/downloads/patches directory. pluby
Post the press release as an article on trinity.neooffice.org. Note: be sure to change the language field from "English" to "All" in when submitting the article so that all Trinity users will see the article. pluby
Post a release announcement to this Trinity forum topic, this Trinity forum topic, and this Trinity forum topic so that the news is included in the RSS feed. pluby

Release

Generally, we try to time the release when it is early morning of the release date in New Zealand which is the most populous country closest to the international date line. So for this release, 15 September 2009 translates to in the afternoon on 14 September 2009 in California.

TaskDate CompletedAssignedStatus
Post the press release as an article on trinity.neooffice.org. Note: be sure to change the language field from "English" to "All" in when submitting the article so that all Trinity users will see the article. pluby
Post a release announcement to this Trinity forum topic, this Trinity forum topic, and this Trinity forum topic so that the news is included in the RSS feed. pluby
Personal tools