From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | "Josh Berkus" <josh(at)agliodbs(dot)com>, pgsql-www(at)postgresql(dot)org |
Subject: | Re: Beta4 release announcement |
Date: | 2010-08-02 17:39:11 |
Message-ID: | 20604.1280770751@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>> Hopefully a clear policy will help prevent similar issues in the
>> future.
> Wasn't part of the problem that the post to -www didn't show up?
> Did anyone answer the question of why announcements are sent to the
> list before they should go out?
Yeah, I don't think that policy statement would have changed a thing.
The correct procedure for sending time-sensitive announcements is
to send them when they should be posted, not to imagine that the
approval queue is a delay mechanism that's under your control.
If you want you can then send something to pgsql-www to pester the
moderators to move quickly.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2010-08-02 18:13:45 | Re: pgsql-announce approvals WAS: Beta4 release announcement |
Previous Message | Kevin Grittner | 2010-08-02 17:21:13 | Re: Beta4 release announcement |