Re: Assembling "top features" list for beta announcement

From: Josh Berkus <josh(at)berkus(dot)org>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Michael Banck <michael(dot)banck(at)credativ(dot)de>, Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: Assembling "top features" list for beta announcement
Date: 2017-04-10 15:37:09
Message-ID: 428799cc-b450-8c1b-6fcd-4c6b58f8225c@berkus.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On 04/09/2017 02:56 PM, Robert Haas wrote:
> On Sun, Apr 9, 2017 at 10:34 AM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>> On 04/08/2017 07:09 PM, Robert Haas wrote:
>>> On Sat, Apr 8, 2017 at 3:48 PM, Josh Berkus <josh(at)berkus(dot)org> wrote:
>>>> From a PR standpoint, 5 is the absolute max, and 3 is better. Really,
>>>> the ideal situation is a set of features which can be closely tied
>>>> together around a simple theme.
>>>
>>> I kinda don't buy this, but I suppose if I had to pick three, I'd pick
>>> partitioning, logical replication, and improved parallel query. If I
>>> could add a fourth I'd add SCRAM, particularly because that really
>>> needs testing and driver support.
>>
>> 3-5 is the sweet spot for a PR. I think SCRAM being listed is a very good
>> thing.
>
> Well, the problem is that everybody's going to have their own ideas on
> what is most important. A release announcement that said
> partitioning, logical replication, and improved parallel query could
> sound dreadfully boring to someone who cares about SCRAM, better query
> planning when RLS is in use, and the default configuration allowing
> replication. I don't suppose there's a whole lot we can do about that
> - we can't list everything - but we're blessed (or cursed) with
> needing to promote a release that really has a ton of great stuff in
> it, and we don't want people to tune out because the stuff they care
> about isn't listed.
>

No quesiton. That's why we divide the beta announcement into two
sections: one with the features we'd like press/reddit/etc. to pick up,
and one with all of the features which we want users to test. This is
different from the final release PR, which will include only the banner
features. To clarify:

Banner Features
---------------

2-5 Features which meet all of:

- will excite the press/twittersphere
- potentially ensnare new users
- can explain to non-DB geeks in 1-2 sentences

Ideally, the above fits around a "theme", but we'll see.

Additional Features
-------------------

3-12 Features which meet any of:

- major features not included in above
- things we really want user testing on
- big API changes
- other stuff we think might grab attention in specific communities

--
Josh Berkus
Containers & Databases Oh My!

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Peter Eisentraut 2017-04-10 15:42:34 Re: Assembling "top features" list for beta announcement
Previous Message Stephen Frost 2017-04-10 13:53:35 Re: Assembling "top features" list for beta announcement