Re: Adjusting to DB2

From: Serge Rielau <srielau_at_ca.ibm.com>
Date: Wed, 26 Oct 2005 09:34:34 -0400
Message-ID: <3s9evnFn3a78U1@individual.net>

Noons wrote:
> Serge Rielau apparently said,on my timestamp of 26/10/2005 9:16 PM:
>

>> Noons wrote:
>>
>>> Mark A apparently said,on my timestamp of 26/10/2005 3:51 PM:
>>>
>>>> Every release and every fixpack on all it's supported platforms. 
>>>> That is because it is more of a single code base than Oracle on the 
>>>> Linux, UNIX, Windows. 
>>>
>>>
>>>
>>>
>>> Or because IBM delays its release on all ports to make it look so?
>>>
>>>
>> That would be an rather suicidal marketing stint even IBM won't pull. 
>> Slipping a release with active customer commitments and IBM internal 

>
> > commitments is not to be taken lightly. With DB2's integration into
>
> "commitments"? Since when? Al it needs is an internal
> memo dictating that all releases happen at the same time.
> And heaps of smoke screen.

What I'm saying is that this ficticeous memo would cost a lot of revenue. From both existing customers who wait for promised features and new customers who delay deploying DB2 because they wait for the newest release.
You are correct that a memo costs nothing. The effect of that memo can be expensive though. That expense is in no relation to the perceived "bragging rights" of simlutaneous releases.

>> SAP's release cycle that's now even less possible than ever.
> That's gonna be fun!...

You bet.

Cheers
Serge

-- 
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab

Received on Wed Oct 26 2005 - 08:34:34 CDT