| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | jd(at)commandprompt(dot)com |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Selena Deckelmann <selenamarie(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: community decision-making & 8.5 |
| Date: | 2009-09-03 15:41:16 |
| Message-ID: | 603c8f070909030841q7b9ed021na8012a5d7cca36c4@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 3, 2009 at 11:38 AM, Joshua D. Drake<jd(at)commandprompt(dot)com> wrote:
> On Thu, 2009-09-03 at 07:44 +0300, Peter Eisentraut wrote:
>> On ons, 2009-09-02 at 12:52 -0700, Joshua D. Drake wrote:
>> > Isn't "core" supposed to be the release manager?
>>
>> The core team has historically been the release *maker* and has some
>> done management of the final phases of that process. But I think the
>> sentiment is growing that we need more management throughout the entire
>> release cycle.
>
> O.k. so a "release" team. Cool. I am assuming the team would be more
> directed toward upcoming major release versus minor releases to past
> revisions. We already pretty much have that under control between -core
> and -packagers. Yes?
+1.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2009-09-03 15:55:49 | Re: community decision-making & 8.5 |
| Previous Message | Joshua D. Drake | 2009-09-03 15:38:36 | Re: community decision-making & 8.5 |