NeoOffice 2.1 Release Tasks

Create NeoOffice-2_1_Early_Access_branch branch from the HEAD branch for NeoOffice 2.1 Early Access so that we can continue to do bug fixes and release Patches while we aer working on this release.

Note: After creating the branch, I invoked the following command in my NeoOffice 2.1 Early Access workspace to ensure that I don't accidently pull NeoOffice 2.1 changes into my build: cvs update -r NeoOffice-2_1_Early_Access_branch

Perform a clean checkout of the HEAD branch and set build to build with a new version and NeoOffice trademarked product name.

This includes the following steps:

• Perform a clean checkout of the HEAD branch
• Copy custom.neo.mk file to custom.mk so that the clean checkout will build with the trademarked product name

• In makefile, change the following macros to the respective values:

  PRODUCT_VERSION=2.1
  PRODUCT_DIR_VERSION=2.1
  PRODUCT_PATCH_VERSION=Patch 0
  PRODUCT_DIR_PATCH_VERSION=Patch-0
  NEO_TAG:=-rHEAD
  

• In this release, there will not be a patch that upgrades a NeoOffice 2.1 Early Access installation so reduce the size of future patches by removing any libraries other than libvcl*.dylib from the build.patch_package target in the makefile
• Commit makefile changes and invoke make build.oo_checkout to checkout the OpenOffice.org code

Upgrade the build to use ooo-build's newer OOO_BUILD_2_1_7 tag.

TODO: Fill in detail steps that I performed

Perform a clean checkout and build of the HEAD branch on Mac OS X 10.4 Intel with gcc 4.0.1.

Note: don't forget to copy custom.neo.mk file to custom.mk so that the clean checkout will build with the trademarked product name

Perform a clean checkout and build of the HEAD branch on Mac OS X 10.4 PowerPC with gcc 3.3.

Note: don't forget to copy custom.neo.mk file to custom.mk so that the clean checkout will build with the trademarked product name

Verify that none of the Intel build binaries link to any X11 libraries.

TODO: Fill in detail steps that I performed

Verify that none of the PowerPC build binaries link to any X11 libraries.

TODO: Fill in detail steps that I performed

Modify and test bin/installutils* sripts to not treat NeoOffice 2.1 Early Access as a match.

In this release, we do not want the installer to preserve the Early Access language pack resource files as some are incompatible with this build and will show as blank text. Also, we don't want the language pack or patch installer to upgrade an Early Access installation as it corrupt that installation.

Note: I tested this code by building the installer, language packs, and patch installer and then doing the following steps:

• Install the patch installer and verify that it does not upgrade my NeoOffice 2.1 Early Access installation.
• Install a NeoOffice 2.1 Early Access language pack, change my machine's preferred language to match the installed language pack, run NeoOffice 2.1 Early Access, and verify that the menus are not English.
• With the same preferred language set in the previous step, install NeoOffice 2.1, and verify that the menus are in English.
• Install a NeoOffice 2.1 language pack, change my machine's preferred language to match the installed language pack, run NeoOffice 2.1, and verify that the menus are not in English and verify that bug 2201 no longer occurs.

Commit and test updated icon files in etc/package.

TODO: Fill in detail steps that I performed

Get latest version of DicOOo.sxw and FontOOo.sxw files, replace all references to the Control key with the Command key, and commit files in etc/share/dict/ooo.

TODO: Fill in detail steps that I performed

Merge any NeoOffice 2.1 Early Access bug fixes committed to the NeoOffice-2_1_Early_Access_branch branch.

Note: As of 03/15/2007, I have already merged the fixes included in NeoOffice 2.1 Early Access Patch 2 Test 1

Tag the code in the HEAD branch with the NeoOffice-2_1 tag.

Note: Because the installer build checks out source code from the anoncvs.neooffice.org server, the following steps must be done to complete this task properly:

• 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.
• In the makefile, set the NEO_TAG macro to NEO_TAG:=-rNeoOffice-2_1 and commit the makefile.
• Tag all files in your workspace by invoking cvs tag NeoOffice-2_1.
• On the cvs.neooffice.org server, run the script to synchronize the anoncvs.neooffice.org server.
• Verify that the installer still builds by deleting the build.source_zip file and invoking make NOLANGPACKS=true.
• If there are any build errors, fix and commit them, retag the changed files by invoking cvs tag -F NeoOffice-2_1, and repeating the previous two steps.

Create releasable NeoOffice 2.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-2_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 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 to create the releasable installer and language packs.

Create releasable NeoOffice 2.1 build for PowerPC.

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