NeoOffice 3.0.2 Release Tasks

From NeoWiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 03:18, 19 January 2010 (edit)
( | contribs)
(Builds - Update task statuses and detail steps)
← Previous diff
Revision as of 15:44, 19 January 2010 (edit) (undo)
( | contribs)
(Builds - Update task statuses)
Next diff →
Line 88: Line 88:
</tr> </tr>
- <tr bgcolor="lightgreen">+ <tr>
<td> <td>
<p>Create backup copy of releasable Intel binaries and upload them to staging server.</p> <p>Create backup copy of releasable Intel binaries and upload them to staging server.</p>
Line 102: Line 102:
</pre> </pre>
</td> </td>
- <td></td><td>pluby</td><td></td>+ <td>01/19/2009</td><td>pluby</td><td>Done</td>
</tr> </tr>
- <tr bgcolor="lightgreen">+ <tr>
<td> <td>
<p>Create backup copy of releasable PowerPC binaries and upload them to staging server.</p> <p>Create backup copy of releasable PowerPC binaries and upload them to staging server.</p>
<p>Note: Use the same steps as used for the matching Intel task.</p> <p>Note: Use the same steps as used for the matching Intel task.</p>
</td> </td>
- <td></td><td>pluby</td><td></td>+ <td>01/19/2009</td><td>pluby</td><td>Done</td>
</tr> </tr>
- <tr bgcolor="lightgreen">+ <tr>
<td> <td>
<p>Verify that the releasable installer and one or more language packs install and run on Intel for the following Mac OS X versions:</p> <p>Verify that the releasable installer and one or more language packs install and run on Intel for the following Mac OS X versions:</p>
Line 122: Line 122:
</ul> </ul>
</td> </td>
- <td></td><td>pluby</td><td></td>+ <td>01/19/2009</td><td>pluby</td><td>Done</td>
</tr> </tr>
- <tr bgcolor="lightgreen">+ <tr>
<td> <td>
<p>Verify that the releasable installer and one or more language packs install and run on PowerPC for the following Mac OS X versions:</p> <p>Verify that the releasable installer and one or more language packs install and run on PowerPC for the following Mac OS X versions:</p>
Line 133: Line 133:
</ul> </ul>
</td> </td>
- <td></td><td>pluby</td><td></td>+ <td>01/19/2009</td><td>pluby</td><td>Done</td>
</tr> </tr>

Revision as of 15:44, 19 January 2010

This page is an attempt to document all of the tasks required to release NeoOffice 3.0.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 assigned
Assigned but not yet due

Contents

Builds

In this release, the total size of the binaries that have bug fixes since we released NeoOffice 3.0.2 Early Access is quite large. So, in order to make room available for any NeoOffice 3.0.2 patches, no upgrade patch will be released.

TaskDate CompletedAssignedStatus

Rebuild all custom NeoOffice code using the existing NeoOffice 3.0.2 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 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=3.0.2
    PRODUCT_DIR_VERSION=3.0.2
    PREVIOUS_PRODUCT_VERSION=$(PRODUCT_VERSION)
    PRODUCT_PATCH_VERSION=Patch 0
    PRODUCT_DIR_PATCH_VERSION=Patch-0
    NEO_TAG:=-rNeoOffice-3_0_2
    
  • 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_0_2_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.
01/18/2009plubyDone

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

Create releasable NeoOffice 3.0.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_0_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_* 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.
01/18/2009plubyDone

Create releasable NeoOffice 3.0.2 build for PowerPC.

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

01/18/2009plubyDone

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.2 directory outside of the workspace
  • Copy all 59 install/*.dmg files from your releasable build into the empty NeoOffice-3.0.2 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.2.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.2.cdr
01/19/2009plubyDone

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.

01/19/2009plubyDone

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.8
  • 10.6.2
01/19/2009plubyDone

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.8
01/19/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 Program main installer binaries are only mirrored on neooffice.org servers so using the above command will only copy the language pack and patch binaries.

TaskDate CompletedAssignedStatus
Upload the 2 NeoOffice main installer NeoOffice-3.0.2-*.dmg files to the joe.neooffice.org server's /neojava/earlyaccessdownloads directory and invoke bin/setpermissions.sh to properly set the permissions of the uploaded files. pluby
Copy the 2 NeoOffice main installer NeoOffice-3.0.2-*.dmg files from the joe.neooffice.org server's /neojava/earlyaccessdownloads directory to the /neojava/downloads directory on all of the mirrors listed in the joe.neooffice.org server's /neojava/includes/earlyaccessmirrors.php file and invoke bin/setpermissions.sh on each server to properly set the permissions of the uploaded files. pluby
Upload the 116 NeoOffice language pack installer NeoOffice-3.0.2-Language_Pack-*.dmg files to the rsync.neooffice.org server's /neojava/downloads directory and invoke bin/setpermissions.sh to properly set the permissions of the uploaded files. pluby
Copy the 116 NeoOffice language pack installer NeoOffice-3.0.2-Language_Pack-*.dmg files from the rsync.neooffice.org server's /neojava/downloads directory to the www.planamesa.net server's /neojava/downloads directory and invoke bin/setpermissions.sh to properly set the permissions of the uploaded files. pluby

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
TaskDate CompletedAssignedStatus
Copy the 2 NeoOffice main installer NeoOffice-3.0.2-*.dmg files from the joe.neooffice.org server's /neojava/earlyaccessdownloads directory to the rsync.neooffice.org server's /neojava/downloads directory and invoke bin/setpermissions.sh on each server to properly set the permissions of the uploaded files. 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: bin/cvsplusperms.sh tag NeoOffice-3_0_2_Early_Access_2 ; bin/cvsplusperms.sh update -d -rNeoOffice-3_0_2_Early_Access_2 pluby

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.2';
    $earlyaccessproductversion = '3.0.2';
    $earlyaccessproductfamily[0] = '3.0.2 Early Access';
    $earlyaccesspatch = '';
    
  • Manually edit all of the earlyaccessdownload.php pages in the /neojava directory and put the "not a production release" warning a "if ($earlyaccessfreeproduct != $earlyaccessproduct)" section.
  • After you verify that the changes look correct, invoke the following command to commit your changes: bin/cvsplusperms.sh commit
pluby
Update the 118 NeoOffice 3.0.2 file sizes and set the 2 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: bin/cvsplusperms.sh commit pluby

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: bin/cvsplusperms.sh tag NeoOffice-3_0_2_Early_Access_2 ; bin/cvsplusperms.sh update -d -rNeoOffice-3_0_2_Early_Access_2 pluby

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 of $earlyaccessproductfamily:
  • $earlyaccessdownloadenabled = false;
    $earlyaccessredirectenabled = true;
    $earlyaccessproductfamily[0] = '';
    $currentproductversion = '3.0.2';
    $currentproductfamily[0] = '';
    $currentpatch = '';
    
  • Manually edit all of the header.html pages in the /neojava directory and update the text in the news banner section.
  • After you verify that the changes look correct, invoke the following command to commit your changes: bin/cvsplusperms.sh commit
pluby
Copy the /neojava/includes/globals/earlyaccessfilesizes.php file to /neojava/includes/globals/filesizes.php and replace all occurrences of earlyaccess with current. If the changes look correct, invoke the following command to commit your changes: bin/cvsplusperms.sh commit pluby

Enable the BitTorrent links using the following steps:

  • Obtain the 2 NeoOffice-3.0.2-*.torrent files from the mirrors.freesmug.org mirror maintainer and bin/cvsplusperms.sh 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: bin/cvsplusperms.sh commit
pluby
Create updated sample.jpg and sample.tiff images using NeoOffice-3.0.2 and put then in the www-test.neooffice.org website's /neojava/images directory and invoke the following command to commit the updated files: bin/cvsplusperms.sh commit pluby
Prepare the NeoOffice_3.0.html press release file, save it in the www-test.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 pluby

Release for Early Access Program

Generally, we release the new version to Early Access Members through the Early Access Program download site a few days before we release the new version to the general public.

TaskDate CompletedAssignedStatus
Verify that all mirrors listed for the NeoOffice 3.0.2 main installer and language pack links work in the www-test.neooffice.org website's Early Access Program download pages. pluby
Append the NeoOffice MD5 checksums page with the NeoOffice 3.0.2 MD5 checksums. pluby
Make the NeoOffice 3.0.2 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 server, cd to the its webroot directory, and invoke the following command: bin/cvsplusperms.sh update -Ad. pluby
Remove the NeoOffice 3.0.2 Early Access MD5 checksums from the NeoOffice MD5 checksums page. pluby
Delete the 2 obsolete NeoOffice 3.0.2 Early Access NeoOffice-3.0.2-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.2 Early Access NeoOffice-3.0.2_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.2 Early Access NeoOffice-3.0.2_Early_Access-Patch-*.dmg patch installer files from the rsync.neooffice.org server's /neojava/downloads directory. pluby
Add "3.0" as a version in Bugzilla. 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"
  • Set "Closed in Version" field to "3.0"
pluby

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"
  • Set "Closed in Version" field to "3.0"
pluby
Post a release announcement to the Trinity forum topic so that the news is included in the RSS feed. pluby
After the files have been deleted from the rsync server, wait 48 hours and verify that these files have been deleted from the mirrors listed in the www.neooffice.org website's /neojava/include/mirrors.php file. Contact any mirror maintainers that still have these files to confirm that they are rsynching to the rsync server regularly. 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, 31 March 2009 translates to in the afternoon on 30 March 2009 in California.

TaskDate CompletedAssignedStatus
Verify that all mirrors listed for the NeoOffice 3.0.2 main installer and language pack links work in the www-test.neooffice.org website's 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: bin/cvsplusperms.sh commit. pluby
Verify that all mirrors listed for the NeoOffice 2.2.5 main installer, language pack, and patch installer links work in the www-test.neooffice.org website's 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: bin/cvsplusperms.sh commit. pluby
Make the NeoOffice 3.0.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
On the neowiki.neooffice.org main page, replace all occurrences of 3.0.1 that are related to NeoOffice with 3.0.2 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 the Trinity forum topic so that the news is included in the RSS feed. pluby
Delete the 2 obsolete NeoOffice 3.0.2 NeoOffice-3.0.2-*.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

Create a new category in the donations database that has a start date and time that is a few hours before the planned release time to ensure that donors who donate after we make the NeoOffice 3.0.2 binaries downloadable get their donation credited to the next Early Access Program using the following steps:

  • Login to the www.neooffice.org server, cd to the /neojava/donationsadmin directory, and execute the following command to add a new category:
    ./manage_categories.php -a
    
  • Set the category_name to Next Planned NeoOffice Early Access Program Membership, the mc_gross_* amounts to the same amounts that were used for the current NeoOffice 3.0.2 Early Access Program Membership category, start_date to 2009-02-01, end date to 2010-12-31, and enabled to 1
  • Run the command again and set the category_name to Next Planned NeoOffice 3.x Early Access Program Subscription, the mc_gross_* amounts to the same amounts that were used for the current NeoOffice 3.x Early Access Program Subscription category, start_date to 2009-02-01, end date to 2010-12-31, and enabled to 1
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 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 current Early Access Program 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
Personal tools