NeoOffice 3.2 Release Tasks

From NeoWiki

This page is an attempt to document all of the tasks required to release NeoOffice 3.2. 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 done

Contents

Builds

Task

Date Completed

Assigned

Status

Rebuild all custom NeoOffice code using the existing NeoOffice 3.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, 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_Beta 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.

Done

pluby

04/15/2011

Tag the code in the HEAD branch with the NeoOffice-3_2 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.

If there are any build errors, fix and commit them, retag the changed files by invoking cvs tag -F NeoOffice-3_2, and repeating the step.

Done

pluby

04/15/2011

Create releasable NeoOffice 3.2 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 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.

Done

pluby

04/15/2011

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 directory outside of the workspace

Copy all 34 install/*.dmg files from your releasable build into the empty NeoOffice-3.2 directory and chmod 444 *.dmg in that directory

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

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

10.7 Developer Preview 2

Done

pluby

04/15/2011

Mirrors

NeoOffice's rsync server is hosted on rsync.neooffice.org. Downloads of the current release are restricted to donors but the previous version is requires no donation to download. Our volunteer mirrors obtain the previous version's binaries by nightly runs of the following command on their mirrors:

Upload the 34 NeoOffice NeoOffice-3.2-*.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

Done

pluby

04/15/2011

Website

Task

Date Completed

Assigned

Status

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: bin/cvsplusperms.sh tag pre_NeoOffice-3_2 ; bin/cvsplusperms.sh update -rpre_NeoOffice-3_2 -d

Done

pluby

04/16/2011

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:

Manually edit all of the header.html 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

Done

pluby

04/16/2011

Update the 34 NeoOffice 3.2 main installer and language pack file sizes and set the patch file size to 0 in the /neojava/includes/globals/filesizes.php file and if the changes look correct, invoke the following command to commit your changes: bin/cvsplusperms.sh commit

Done

pluby

04/16/2011

Update the 70 NeoOffice 3.1.1 main installer, language pack, and patch file sizes in the /neojava/includes/globals/oldfilesizes.php file and if the changes look correct, invoke the following command to commit your changes: bin/cvsplusperms.sh commit

Done

pluby

04/16/2011

cvs remove the 2 NeoOffice 3.0.2 torrent files in the /neojava/downloads directory and if the changes look correct, invoke the following command to commit your changes: bin/cvsplusperms.sh commit

Done

pluby

04/16/2011

Prepare the NeoOffice_3.2.html press release file, save it in the www-test-primary.neooffice.org website's /press_releases directory using the following naming format, bin/cvsplusperms.sh add the file, and invoke the following command to commit the new file: bin/cvsplusperms.sh commit

Done

pluby

04/19/2011

Verify that patch checking works properly by doing the following steps in a NeoOffice 3.2 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:

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:

Test as NeoOffice 3.1.2 Patch 8 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:

Test as NeoOffice 3.2 Beta Patch 2 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:

Test as NeoOffice 3.2 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.

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, 19 April 2011 translates to the early afternoon on 18 April 2011 in California.

Task

Date Completed

Assigned

Status

Verify that all mirrors listed for the NeoOffice 3.2 main installer and language pack links work in the www-test-primary.neooffice.org website's download pages. If any do not work, comment them out in the /neojava/includes/mirrors.php file and invoke the following command: bin/cvsplusperms.sh commit

pluby

Make the NeoOffice 3.2 binaries downloadable from the www.neooffice.org website's 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 server, cd to the its webroot directory, and invoke the following command: bin/cvsplusperms.sh update -Ad

pluby

Make NeoOffice 3.2 the current version in the NeoWiki using the following steps:

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"

Set "Closed in Version" field to "3.2"

pluby

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"

Set "Closed in Version" field to "3.2"

pluby

Post the press release as an article on the Trinity news page. 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.

Delete the 34 obsolete NeoOffice-3.2_Beta-*.dmg main installer and language pack files from the /neojava/downloads directory on all of the mirrors listed in the rsync.neooffice.org server's /neojava/includes/mirrors.php file.

pluby

Delete the 68 obsolete NeoOffice-3.0.2-*.dmg main installer and language pack files from the /neojava/downloads directory on all of the mirrors listed in the rsync.neooffice.org server's /neojava/includes/mirrors.php file.

pluby

Delete the obsolete NeoOffice-3.2_Beta-*.dmg patch installer files from the /neojava/downloads/patches directory on all of the mirrors listed in the rsync.neooffice.org server's /neojava/includes/mirrors.php file.

pluby

Delete the obsolete NeoOffice-3.0.2-*.dmg patch installer files from the /neojava/downloads/patches directory on all of the mirrors listed in the rsync.neooffice.org server's /neojava/includes/mirrors.php file.

pluby

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: