Re: Heroku early upgrade is raising serious questions

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Jean-Paul Argudo <jean-paul(at)postgres(dot)fr>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-advocacy(at)postgresql(dot)org
Subject: Re: Heroku early upgrade is raising serious questions
Date: 2013-04-15 08:23:09
Message-ID: m2r4icw6c2.fsf@2ndQuadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

Jean-Paul Argudo <jean-paul(at)postgres(dot)fr> writes:
> The fundamental question then, is how organizations qualify to become
> "trusted organizations" ?

From my understanding of the current situation, it's quite easy and
clear, arrange to be subscriber on pgsql-packagers.

Maybe what we need to do is document that to get early access to
security updates you need to be registered as a packager, and that we
only accept trusted person in there.

Then any packager is trusted to release the upgrade either in the open
following the public rules, or otherwise as he sees fit with *explicit
approval* from core.

The procedure certainly would need to be specific that should you fail
to follow those 2 easy to document cases, you can get removed from the
packagers list.

> Lots of people on this list, and Im part of it, want to have users
> treated equally and carrefully.

I can't resist, please don't mix equality and equity. See attached, as
pictures work so much better than written words.

Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support

Attachment Content-Type Size
image/jpeg 66.7 KB

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Selena Deckelmann 2013-04-15 15:39:29 Re: Heroku early upgrade is raising serious questions
Previous Message Jean-Paul Argudo 2013-04-15 07:42:57 Re: Heroku early upgrade is raising serious questions