Re: Heroku early upgrade is raising serious questions

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(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 00:13:47
Message-ID: 51635D3B.30802@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On 04/08/2013 04:32 PM, Joshua D. Drake wrote:
>
> On 04/08/2013 04:12 PM, Josh Berkus wrote:
>>
>
>> Clearly we can't do it that way again.
>>
>> -core is currently hashing out thoughts on what might be a reasonable
>> early notification process for high-risk users, and if it's feasible for
>> us to have one. As well as other aspects of our security release
>> procedure.
>>
>
> I think that one thing that is very important to remember here, is -core
> doesn't make decisions lightly. I understand that some may have felt
> that communication wasn't perfect (it wasn't) but I know several members
> of core and they all take the position IMHO too seriously. So let's
> relax, realize there is improvement to be made (which they and we do)
> and just work the problem.

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.

>
> The rest is just noise.
>
> Sincerely,
>
> JD
>
>
>
>
>

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Josh Berkus 2013-04-09 00:50:32 Re: Heroku early upgrade is raising serious questions
Previous Message Bruce Momjian 2013-04-08 23:32:21 Re: Heroku early upgrade is raising serious questions