| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | damien clochard <damien(at)dalibo(dot)info> |
| Cc: | Dave Page <dpage(at)pgadmin(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, "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 15:37:53 |
| Message-ID: | 516435D1.5020506@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On 04/09/2013 01:38 AM, damien clochard wrote:
>>> 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.
>>
>> I'm not arguing either way here... but if you think of DBaaS as "the
>> new packaging", it starts to seem more reasonable to give folks like
>> Heroku access at the same time as the traditional packagers.
>>
>
> Just to make things clear : my previous message is not about wether or
> nor a DBaaS provider should have early access to security releases (even
> if that's a good question).
>
> My message is about wether or not a DBaaS provider should be allowed to
> deploy the security release days before the official release date.
>
Right. Which I don't think they should be able to.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2013-04-09 15:39:03 | Re: Heroku early upgrade is raising serious questions |
| Previous Message | Matteo Beccati | 2013-04-09 13:27:29 | Re: elephant logo in OFM format? |