NeoOffice 2.1 Release Tasks

From NeoWiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 06:16, 15 March 2007 (edit)
Pluby (Talk | contribs)

← Previous diff
Revision as of 06:25, 15 March 2007 (edit) (undo)
Pluby (Talk | contribs)
(Add overview to Builds section)
Next diff →
Line 1: Line 1:
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. 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.
 +
== Builds == == 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.
<table width="100%" border="1"> <table width="100%" border="1">
Line 43: Line 46:
<td> <td>
<p>Upgrade the build to use ooo-build's newer OOO_BUILD_2_1_7 tag.</p> <p>Upgrade the build to use ooo-build's newer OOO_BUILD_2_1_7 tag.</p>
 + <p>'''TODO: Fill in detail steps that I performed'''</p>
</td> </td>
<td>03/14/07</td><td>pluby</td><td>Done</td> <td>03/14/07</td><td>pluby</td><td>Done</td>
Line 48: Line 52:
</table> </table>
 +
== Website == == Website ==
 +
== Mirrors == == Mirrors ==
Line 81: Line 87:
</table> </table>
 +
== Release == == Release ==

Revision as of 06:25, 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


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