Re: Heroku early upgrade is raising serious questions

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, damien clochard <damien(at)dalibo(dot)info>, "Jonathan S(dot) Katz" <jonathan(dot)katz(at)excoventures(dot)com>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: Heroku early upgrade is raising serious questions
Date: 2013-04-09 01:20:18
Message-ID: 51636CD2.8050305@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy


On 04/08/2013 05:50 PM, Josh Berkus wrote:
>
>
>> Agreed. As far as I can see things where handled in the Postgres way,
>> when in doubt err on the side of caution. I applaud the efforts of those
>> concerned and trust in their ability to build on the experience.
>
> Mostly I'd rather be arguing as to whether or not we should have given
> Heroku early deployment

No.

That isn't to say I didn't understand that theory of doing so. I do.
However, you essentially created a class of user that is above other
users and that is explicitly not Open Source.

Sincerely,

Joshua D. Drake

--
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC
@cmdpromptinc - 509-416-6579

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Adrian Klaver 2013-04-09 02:16:09 Re: Heroku early upgrade is raising serious questions
Previous Message Josh Berkus 2013-04-09 00:50:32 Re: Heroku early upgrade is raising serious questions