Mr. Cohen,

Before I got saddled with an ORACLE legacy application that is miring me in
5.5 I used this upgrade strategy:
1. "Pull" releases when the functionality warranted it. This also applies to
patches and Express releases.
2. "Push" releases within the first year (i.e. when I had a free weekend) or
if there was a new and needed functionality.
3. Reactive patches as needed.

I personally think the best idea was this:
o  Should we "Push" at all? Would you prefer simply to receive the
   Communicator once we come out with a release, and you can decide
   whether you want it?

Send out the communicator. This would inform us that a new release is
imminent. Those that wish to upgrade can request the release. Those that
wish to wait can wait.

This means that you don't send a tape to those that don't need it. It also
means that  when a release is requested it could then be send out in its
latest version, i.e. if power patches exist they have been incorporated in
the release. This would make installation easier.

I would be willing to wait an extra week to receive my tape or CD (read I
can order it a week earlier) if it meant cutting out steps in the
installation.

Thanks for asking and thanks for listening.

Joseph Rosenblatt