Re: Heroku early upgrade is raising serious questions - Mailing list pgsql-advocacy

From Jonathan S. Katz
Subject Re: Heroku early upgrade is raising serious questions
Date
Msg-id 5A951C2A-6078-46BD-87EB-0085A9D800C3@excoventures.com
Whole thread Raw
In response to Re: Heroku early upgrade is raising serious questions  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Heroku early upgrade is raising serious questions
List pgsql-advocacy
On Apr 8, 2013, at 2:53 PM, Joshua D. Drake wrote:

>
> On 04/08/2013 11:49 AM, Jonathan S. Katz wrote:
>> On Apr 3, 2013, at 1:46 PM, Josh Berkus wrote:
>
>> Josh - I think your points are valid concerning the vetting of who would
>> be included in early releases.  I believe the best way to address who
>> would be on that list is having a committee to vet those applications -
>> I believe that is similar to how other OSS communities handle it.  I do
>> not think the amount of submissions for requesting early access would be
>> so great that we would need a full-time team to maintain it, and I think
>> most of us have a good idea already about which types of organizations
>> truly would need an early access release.
>>
>> With that said, if there are no overwhelming objections over the next 36
>> hours, I can submit a patch to our security policy on the website using
>> the language that is in the wiki above.
>
> Since it is -core that primarily decides when things will be released, it seems that we would need their approval for
thispolicy? 

Well, that would be valid.  Could someone in -core please put the policy through the proper procedural work for
approval?

Jonathan



pgsql-advocacy by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Heroku early upgrade is raising serious questions
Next
From: "Jonathan S. Katz"
Date:
Subject: Re: elephant logo in OFM format?