Skip site navigation (1) Skip section navigation (2)

Re: [pgsql-advocacy] Avoiding upgrade backlash

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, josh(at)agliodbs(dot)com, pgsql-docs(at)postgresql(dot)org
Subject: Re: [pgsql-advocacy] Avoiding upgrade backlash
Date: 2007-11-17 21:09:26
Message-ID: 473F5886.8040702@commandprompt.com (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-docs
Bruce Momjian wrote:
> Joshua D. Drake wrote:
>> Tom Lane wrote:
>>> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
>>>> Honestly, I think you are underestimating this problem.
>>> I fail to see why this is a major problem; and merely asserting that
>>> it is one isn't going to change my mind.  Can you point to something
>>> like a major application that will be broken and can't easily be fixed?
>> SQL-Ledger/LedgerSMB
>>
>> What I find interesting is that I (and Josh) are getting push back and 
>> all we are trying to do is be a little louder about the change.
> 
> Adding extra warnings/notices is not a zero-cost action so there has to
> be justification to do it.  Actually it is near-zero cost to use but not
> zero-cost to our users who have to read it multiple places.  (Think dumb
> product warning labels.)
> 
> What I have done is to move the item up to the top of our
> incompatibilities list in the release notes.  That is near zero cost for
> everyone.
> 

Thank you.

Joshua D. Drake


In response to

pgsql-docs by date

Next:From: Theo KramerDate: 2007-11-18 09:15:03
Subject: Re: [pgsql-advocacy] Avoiding upgrade backlash
Previous:From: Bruce MomjianDate: 2007-11-17 21:05:50
Subject: Re: [pgsql-advocacy] Avoiding upgrade backlash

pgsql-advocacy by date

Next:From: Theo KramerDate: 2007-11-18 09:15:03
Subject: Re: [pgsql-advocacy] Avoiding upgrade backlash
Previous:From: Bruce MomjianDate: 2007-11-17 21:05:50
Subject: Re: [pgsql-advocacy] Avoiding upgrade backlash

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group