NeoOffice 2.1 Release Tasks

From NeoWiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 17:09, 15 March 2007 (edit)
OPENSTEP (Talk | contribs)
(Builds - claim PPC release build eng.)
← Previous diff
Revision as of 21:09, 15 March 2007 (edit) (undo)
Pluby (Talk | contribs)
(Add two new tasks)
Next diff →
Line 15: Line 15:
<td> <td>
<p>Create <tt>NeoOffice-2_1_Early_Access_branch</tt> 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.</p> <p>Create <tt>NeoOffice-2_1_Early_Access_branch</tt> 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.</p>
- <p>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: <tt>cvs update -r NeoOffice-2_1_Early_Access_branch</tt></p>+ <p>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: <tt>cvs update -r NeoOffice-2_1_Early_Access_branch</tt></p>
</td> </td>
<td>03/13/07</td><td>pluby</td><td>Done</td> <td>03/13/07</td><td>pluby</td><td>Done</td>
Line 65: Line 65:
</td> </td>
<td>03/16/07</td><td>OPENSTEP</td><td></td> <td>03/16/07</td><td>OPENSTEP</td><td></td>
 + </tr>
 +
 + <tr>
 + <td>
 + <p>Modify and test <tt>bin/installutils*</tt> sripts to not treat NeoOffice 2.1 Early Access as a match.</p>
 + <p>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.</p>
 + <p>Note: I tested this code by building the installer, language packs, and patch installer and then doing the following steps:</p>
 + <ul>
 + <li>Install the patch installer and verify that it does not upgrade my NeoOffice 2.1 Early Access installation.</li>
 + <li>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.</li>
 + <li>With the same preferred language set in the previous step, install NeoOffice 2.1, and verify that the menus are in English.</li>
 + <li>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 [http://bugzilla.neooffice.org/bug.php?op=show&bugid=2201&pos=0 bug 2201] no longer occurs.</li>
 + </ul>
 + </td>
 + <td>03/15/07</td><td>pluby</td><td>Done</td>
 + </tr>
 +
 + <tr>
 + <td>
 + <p>Merge any NeoOffice 2.1 Early Access bug fixes committed to the <tt>NeoOffice-2_1_Early_Access_branch</tt> branch.</p>
 + <p>Note: As of 03/15/2007, I have already merged the fixes included in NeoOffice 2.1 Early Access Patch 2 Test 1</p>
 + </td>
 + <td>03/18/07</td><td>pluby</td><td></td>
</tr> </tr>

Revision as of 21:09, 15 March 2007

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


Contents

Builds

In this release, there is no change in the OpenOffice.org tag that we are using so this build is far simpler than the NeoOffice 2.1 Early Access build. However, in order to fix a few ooo-build bugs found in NeoOffice 2.1 Early Access, we need to upgrade to a newer ooo-build tag. Also, we are going to bundle the latest Akua icon set. These two changes will mean that in this release, there will not be a patch that upgrades a NeoOffice 2.1 Early Access installation.

TaskDue DateAssignedStatus

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

03/13/07plubyDone

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
03/14/07plubyDone

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

TODO: Fill in detail steps that I performed

03/14/07plubyDone

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

03/14/07plubyDone

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

03/16/07OPENSTEP

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.
03/15/07plubyDone

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

03/18/07pluby

Website

Mirrors

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

rsync -r --delete rsync://www.heapsys.com/ftp/ /path/to/NeoOffice/mirror/directory
TaskDue DateAssignedStatus
Notify rsync server and mirrors that we will be pushing new binaries out to them a few days before the 27 March 2007 release date so that they can prepare for the huge surge in bandwidth usage that their servers will get in the first month or so after reelease. 03/12/07plubyDone
Provide list of URLs of binaries and their respective file sizes to the rsync server so that the rsync server can copy them to the rsync server. 03/21/07pluby
Verify that the binaries are available from the rsync server and verify that each of the mirrors has synched them to their site. Try to contact any mirrors that have not synched to see if their is any problem or if the site can no longer be a mirror. 03/23/07pluby


Release

Personal tools