|
NeoOffice 3.0.1 Early Access Release Tasks
From NeoWiki
This page is an attempt to document all of the tasks required to release NeoOffice 3.0.1 Early Access. 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, a new OpenOffice.org tag was used. Also, new application and toolbar icons were added. Because of these changes, an upgrade patch would be excessive large so no upgrade patch will be released.
Task | Date Completed | Assigned | Status |
Verify that OpenOffice.org does not have a newer tag for version 3.0.1.x than the OOO300_m14 tag. |
pluby | ||
Verify that ooo-build does not have a newer tag than the OOO_BUILD_3_0_1 branch. |
pluby | ||
Verify that Novell's patched odf-converter does not have a newer version than 2.5-2 in Novell's odf-converter source repository. |
pluby | ||
Commit and test updated icon files in etc/package.
|
07/08/2009 | pluby | Done |
Since NeoOffice 3.0.1 Early Access has code changes in the Go-oo portion of the build, perform a clean build by doing a complete checkout of the HEAD branch in a new, empty directory and building the entire NeoOffice product from scratch. This includes the following steps:
|
08/21/2009 | pluby | Done |
Rebuild all custom NeoOffice code using the existing NeoOffice 2.2.5 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 and RetroOffice trademarked product names. This includes the following steps:
|
08/21/2009 | pluby | Done |
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 . -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) |
pluby | ||
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. |
pluby | ||
Tag the code in the HEAD branch with the NeoOffice-3_0_1_Early_Access tag using the following:
|
08/21/2009 | pluby | Done |
Tag the code in the NeoOffice-2_2_6_branch branch with the NeoOffice-2_2_6_Early_Access tag using the following:
|
08/21/2009 | pluby | Done |
Create releasable NeoOffice 3.0.1 Early Access build for Intel. Note: the following steps are overkill, but they ensure that all recent changes to the NeoOffice custom code has been built:
|
pluby | ||
Create releasable NeoOffice 3.0.1 Early Access build for PowerPC. Note: Use the same steps as used for the matching Intel task. |
pluby | ||
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:
Put the NeoOffice-3.0.1_Early_Access folder in a new empty directory and create a CD master NeoOffice-3.0.1_Early_Access.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_Early_Access.cdr |
pluby | ||
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. |
pluby | ||
Verify that the releasable installers and one or more language packs install and run on Intel for the following Mac OS X versions:
|
pluby | ||
Verify that the releasable installers and one or more language packs install and run on PowerPC for the following Mac OS X versions:
|
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
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 and patch binaries.
Task | Date Completed | Assigned | Status |
Upload the 2 NeoOffice main installer NeoOffice-3.0.1_Early_Access-*.dmg files to the joe.neooffice.org server's /neojava/earlyaccessdownloads directory. | pluby | ||
Copy the 2 NeoOffice main installer NeoOffice-3.0.1_Early_Access-*.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. | pluby | ||
Upload the 116 NeoOffice language pack installer NeoOffice-3.0.1_Early_Access-Language_Pack-*.dmg files to the joe.neooffice.org server's /neojava/downloads directory. | pluby | ||
Copy the 116 NeoOffice language pack installer NeoOffice-3.0.1_Early_Access-Language_Pack-*.dmg files from the rsync.neooffice.org server's /neojava/downloads directory to the www.planamesa.net server's /neojava/downloads directory. | pluby |
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: cvs tag NeoOffice-2_2_5 ; cvs update -d -rNeoOffice-2_2_5 ; chmod -Rf ug+rw .[ch]* * | 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:
$earlyaccessdownloadenabled = true; $earlyaccessredirectenabled = false; $earlyaccessfreeproduct = 'NeoOffice 3.0.1'; $earlyaccessproductversion = '3.0.1 Early Access'; $earlyaccessproductfamily[0] = ''; $earlyaccesspatch = 'Patch 0'; |
pluby | ||
Update the 118 NeoOffice 3.0.1 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 ; chmod -Rf ug+rw .[ch]* * | 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 ; chmod -Rf ug+rw .[ch]* *. 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 ; chmod -Rf ug+rw .[ch]* * | 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.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 ; chmod -Rf ug+rw .[ch]* * |
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.
Task | Date Completed | Assigned | Status |
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:
|
pluby | ||
Verify that all mirrors listed for the NeoOffice 3.0.1 Early Access 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: cvs commit ; chmod -Rf ug+rw .[ch]* *. | pluby | ||
Make the NeoOffice 3.0.1 Early Access 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: cvs update -Ad ; chmod -Rf ug+rw .[ch]* *. | pluby | ||
Append the NeoOffice MD5 checksums page with the NeoOffice 3.0.1 Early Access MD5 checksums. | pluby | ||
Add "3.0.1 EA" as a version in Bugzilla. | pluby | ||
Close all bugs with a status of "Resolved" by setting the following field values:
|
pluby | ||
Close any bugs with a status of "Assigned" or "Reopened" and resolution of "Fixed" (bugs fixed in the release build after the final Early Access patch) by setting the following field values:
|
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 NeoJUpdate mailing list. | pluby | ||
Post a release announcement to the Trinity forum topic so that the news is included in the RSS feed. | pluby |