|
|
NeoOffice 2.1 Release Tasks
From NeoWiki
| Revision as of 03:50, 15 March 2007 (edit) ( | contribs) (Add branch creation task) ← Previous diff |
Revision as of 05:41, 15 March 2007 (edit) (undo) ( | contribs) (Document steps for changing version in build) Next diff → |
||
| Line 2: | Line 2: | ||
| <table width="100%" border="1"> | <table width="100%" border="1"> | ||
| - | <tr> | + | <tr> |
| - | <td><b>Task</b></td><td width="10%"><b>Due Date</b></td><td width="10%"><b>Assigned</b></td><td width="10%"><b>Status</b></td> | + | <td><b>Task</b></td><td width="10%"><b>Due Date</b></td><td width="10%"><b>Assigned</b></td><td width="10%"><b>Status</b></td> |
| - | </tr> | + | </tr> |
| - | <tr> | + | |
| - | <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> | + | <tr> |
| - | <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>03/13/07</td><td>pluby</td><td>Done</td> | + | <td> |
| - | </tr> | + | <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> |
| - | <tr> | + | <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><p>Upgrade build to use ooo-build's newer OOO_BUILD_2_1_7 tag.<p></td><td>03/14/07</td><td>pluby</td><td>Done</td> | + | </td> |
| - | </tr> | + | <td>03/13/07</td><td>pluby</td><td>Done</td> |
| + | </tr> | ||
| + | |||
| + | <tr> | ||
| + | <td><p>Perform a clean checkout of the HEAD branch and set build to build with a new version and NeoOffice trademarked product name.</p> | ||
| + | <p>This includes the following steps:</p> | ||
| + | <ul> | ||
| + | <li>Perform a clean checkout of the HEAD branch</li> | ||
| + | <li>Copy <tt>custom.neo.mk</tt> file to <tt>custom.mk</tt> so that the clean checkout will build with the trademarked product name</li> | ||
| + | <li> | ||
| + | <p>In <tt>makefile</tt>, change the following macros to the respective values:</p> | ||
| + | <pre> | ||
| + | PRODUCT_VERSION=2.1 | ||
| + | PRODUCT_DIR_VERSION=2.1 | ||
| + | PRODUCT_PATCH_VERSION=Patch 0 | ||
| + | PRODUCT_DIR_PATCH_VERSION=Patch-0 | ||
| + | NEO_TAG:=-rHEAD | ||
| + | </pre> | ||
| + | </li> | ||
| + | <li>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 <tt>libvcl*.dylib</tt> from the <tt>build.patch_package</tt> target in the <tt>makefile</tt></li> | ||
| + | <li>Commit <tt>makefile</tt> changes and invoke <tt>make build.oo_checkout</tt> to checkout the OpenOffice.org code</li> | ||
| + | </ul> | ||
| + | </td><td>03/14/07</td><td>pluby</td><td>Done</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td> | ||
| + | <p>Upgrade the build to use ooo-build's newer OOO_BUILD_2_1_7 tag.</p> | ||
| + | </td><td>03/14/07</td><td>pluby</td><td>Done</td> | ||
| + | </tr> | ||
| </table> | </table> | ||
Revision as of 05:41, 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.
| Task | Due Date | Assigned | Status |
|
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/07 | pluby | Done |
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:
| 03/14/07 | pluby | Done |
|
Upgrade the build to use ooo-build's newer OOO_BUILD_2_1_7 tag. | 03/14/07 | pluby | Done |
