| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Josh berkus <josh(at)agliodbs(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: Beta1 announcement: alpha1 draft |
| Date: | 2016-04-27 02:37:31 |
| Message-ID: | 572025EB.6090805@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On 04/26/2016 07:21 PM, Robert Haas wrote:
> I am not opposed to promoting those things; I just don't think it
> belongs in the beta announcement.
>
Fair enough.
What would you suggest as an alternative? I exclusively speak to
practitioners. The people doing the lifting after we release. A constant
question is about tools. Heck, most of the time it isn't, "when will we
support X", it is more, "what tool would help me do Y?"
It seems that an announcement of a Beta is a perfect opportunity without
taking away from the release itself. That said, is there something you
think would be more appropriate? Do you think we should advocate a
"toolset" or some such thing? I love the idea of a .Org extended toolset.
Sincerely,
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-04-27 02:46:43 | Re: Beta1 announcement: alpha1 draft |
| Previous Message | Robert Haas | 2016-04-27 02:21:32 | Re: Beta1 announcement: alpha1 draft |