From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, Justin Clift <justin(at)postgresql(dot)org>, pgsql-www(at)postgresql(dot)org |
Subject: | Re: New News Entry |
Date: | 2004-06-18 23:16:43 |
Message-ID: | 20040618201515.Y17561@ganymede.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Fri, 18 Jun 2004, Josh Berkus wrote:
> Folks,
>
> My personal opinion on policy:
>
> For software (or hardware) which is not PostgreSQL community, but is "useful"
> or "newsy" as we define it, we announce it when it either
> 1) goes production for the first time,
> 2) supports postgresql for the first time
> and never post news about that particular piece of software again unless
> there's a compelling reason to make an exception.
I'd extend 2 to include major version releases ...
> For software which is PostgreSQL community, we allow announcements when it:
> 1) is created as a project;
> 2) first goes beta (if it needs testers);
> 3) first goes production;
> 4) achieves a major (e.g. 2.0) version milestone
Sounds reasonable to me ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2004-06-18 23:21:53 | Re: New News Entry |
Previous Message | Josh Berkus | 2004-06-18 22:38:49 | Re: New News Entry |