OO 3 on the way (or not, depending on what you mean by on the way)

[Stephen Chakwin]

On 7/27/04 6:42 PM, "James Moore" <jam at omnigroup.com> wrote:

> You don't have to speculate about why the schedule has slipped.

But it's hard to avoid since it was such an eagerly awaited event.
> 
> We now know that when you re-write an app from scratch you can't also
> decide to add loads of new features unless you want it to take almost
> two years to complete.

Didn't know that this was what you were up to.  A rewrite from scratch is
obviously a big deal.  Perhaps you (institutionally) could have made that
more clear.

> 
> The development and testing of OO3 is progressing at a rapid pace now.
> We've got a schedule that is working for us and I believe I know about
> when we're going to ship. I'm hesitant to be more specific about the
> projected ship date because so much non-engineering work is left to do.

OK.  It seems less than rapid from outside because of early word about a
potential June release date.  And then it seemed that features that had been
in play were backed away from.  In the context of a rewrite from scratch,
this makes sense.  In terms of what I thought we were told it didn't.
> 
> I believe that you guys are gonna love Outliner 3. I know its a drag
> that its taken so long. I highly doubt future major releases will take
> so long to complete.

I hope you're right about these predictions.  I believe in the product and
so am willing to believe that all of this is so.
> 
> 
> -James
> 

Thanks for the detailed and patient (read - engineer's) response.

Stephen

> Technical Support Engineer
> The Omni Group
> 
> On Jul 27, 2004, at 1:11 PM, Stephen Chakwin wrote:
> 
>> It's good to hear that it's coming, but disappointing to learn that
>> what we
>> had thought was coming in early June with more features lost features
>> and
>> slipped back half a year.
>> 
>> I don't want to speculate about why this might have happened or invite
>> you
>> and your colleagues to share the thinking with us (which I recognize
>> would
>> be an invitation not likely to be accepted).  But I didn't want to let
>> the
>> news pass unmarked.  I was looking forward to the new features and
>> hoping to
>> have them in use before next year, which now seems unlikely.
>> 
>