readme-distribution

彩信浏览器

Creating the MacOSX installer
=============================

- First build all the needed third party packages as universal
  binaries: ffmpeg, live, sdl, expat, xerces.
  third_party_packages/readme.txt has (terse) instructions on
  how to do this.
  SDL needs to be installed, the others are used in-place.
- Build the whole source tree, don't forget options for
  enabling xerces, etc. You want to build with Xerces in a plugin,
  live support, no Python support, only fast internal DOM acces,
  i.e. with
    ../configure -C --with-ffmpeg --without-external-dom \
        --without-python --with-live \
        --with-xerces --with-xerces-plugin \
        --with-universalsdk --disable-dependency-tracking
- The build will fail at the cocoambulant_executable link. See
  src/player_macosx/README on how to proceed.
- Install the player in src/player_macos.
- Create a folder called something like "Ambulant Player 1.6", 
  and copy the items mentioned above into it.
- Use Applications->Utilities->Disk Utilities to create a .dmg
  disk image from this folder (read only, compressed). Make sure the
  version number is part of the disk image name.
  
Creating the Windows desktop installer
======================================

Build the player. Make sure you are building a *Release* player,
not a *Debug* player.

Open src/AmbulantWin32Installer/AmbulantWiseInstaller.wse with Wise.
Make sure the files mentioned above are included. If you need to add more
files: Wise will use absolute paths by default (for the source files), you
want to turn these into relative paths.

The installer will be deposited in bin/win32. You need to change the filename
to include the version number.

Creating the Windows CE installer
=================================

Build the player. Make sure you are building a *Release* player,
not a *Debug* player.

Open src/AmbulantWin32Installer/AmbulantWinCEWiseInstaller.wse with Wise.
The procedure is pretty similar as for the desktop windows player, the
installer ends up in bin/wince.

Creating the Zaurus installer
=============================

To be supplied.

Creating the Linux installer
============================

For this release we will probably not do Linux binary installers,
but as we have done one before we should write down the procedure here.


Testing the distributions
=========================

Here are some random remarks about testing the distributions. Note that
during the distribution test period it is important to be thorough and
precise. If you save yourself a few minute of effort by not testing
something or not reporting a problem this may well result in an extra
bugfix release later (which will cost everyone another 2 days or so of work).

- IMPORTANT: while we are testing distributions we want to make absolutely
  sure that any bugs are either (a) fixed or (b) acknowledged as known bugs.
  Therefore, if you find a bug that you think may be critical you *must*
  submit a bug report with high priority and assign to the release czar
  (probably Jack).

- The Mac player must definitely be tested on a virgin machine,
  to ensure there are no dependencies on dynamic libraries in /usr/local
  or something like that.
  
- The Mac player must also be tested on older MacOS releases (at least the
  oldest supported), and either be made to run or the minimum required
  OS version adapted.
  
- On all platforms, test either on a virgin machine or at least
  clear out preferences before testing (unix: $HOME/.ambulant;
  mac: ~/Library/Preferences/org.ambulantplayer.ambulantplayer.plist;
  windows: HKEY_CURRENT_USER\Software\Ambulant\AmbulantPlayer in the registry).
  
- On windows, test on at least Win98, Win2K and WinXP.
  
- Make sure Welcome plays at first run. Check that the preferences have
  sensible defaults (log level: trace, parser: expat, log window: closed).

- Then play DemoPresentation/NYC-SMIL2.smil.
  Then play the website documents. Use the Xerces parser. Open the log window,
  select "debug" output, and make sure that there aren't any accidental
  AM_DBG's left on.
  
- For each platform, try and get someone knowledgable with the platform but
  not the Ambulant Player to build the distribution.
  
- On the platforms that support it (Linux, Mac) test localisation. We
  should have at least English and Dutch working.
  
- On each platform, check that the version numbers are correct in things
  like the about dialog, Get Info (Properties) in the Finder (Explorer), etc.

- We can use vin.cst.cwi.nl to test it on newer distributions then our desktop.
  (at this moment fedora core 3)

  
Uploading the distributions
===========================

Adding a new file release package
---------------------------------
A release package is a collection of file releases (binary as well as
source) for different platforms but the with same version number. To add
a SF release package choose in the admin menu File Releases. At the
bottom of the page you will find a field where you can add the name of a
new release package. We have to use different names for our release
packages. (such that the latest release is always on top). I propose to
use the following naming scheme, Ambulant <version number> (eg Ambulant
1.0, Ambulant 1.2). The minor release number is always even for stable
releases, the development version uses the uneven numbers.

Adding file releases to a release package
-----------------------------------------
To add files to a release package choose in the admin menu File
releases. At the bottom you will find an overview of all the release
packages, click on Add Release next to the release package  you want to
add a release to. You will be asked a release new release name. Make
sure this name is a unique name (so we can easily track it down in the
SF stats). The next step is to upload and add the file belonging to the
release. Upload the file to upload.sourceforge.net and click on Edit
Releases belonging to the release package your editing in the package
overview, and click again on edit release next to the release you want
to add a file to. Fill in the neccesary information in Step 1, and
select the file in Step 2. In Step 3 fill in the right processor type
and file type for the released file.

Proposed naming scheme for release names:

- Binary packages: ambulant-<versionnumber>-<platform>.ext (eg. for
  windows ambulant-1.2-win32.exe, for mac ambulant-1.2-osx.dmg).
- Source package: I think the name make distcheck gives to the package is
  fine. eg ambulant-1.2.tar.gz. Don't use ".tgz", winzip doesn't like it.

Again the minor release number indicates a stable release if the number is even.


Hiding a file release package
-----------------------------
Make sure that all file releases belonging to a file release package are hidden.
If not, you can not hide the release package and it will stay active.

Updating the website
====================

To be supplied. Here are some random thoughts:
- The design and API docs need to be uploaded
- The SMIL documents need to be uploaded (if changed)



Advertising the distributions
=============================

To be supplied. Some ideas, plus who knows how to submit things:
- ambulant-announce
- ambulant-users
- www-smil
- W3C (Dick)
- NLnet (Dick)
-   http://guide.apple.com/usindex.lasso (jack)
-   http://www.apple.com/downloads/macosx/submit (jack)
-   http://www.versiontracker.com/ (jack, userid [e-mail])
-   http://www.macshareware.net (jack, userid jackjansen)
-	A macpad file is in www.cwi.nl/~jack/macpad. There's a pad file there too.
-   [e-mail] (jack)
-   http://www.macupdate.com (jack)
-   http://www.tucows.com (jack, username ambulant)