MIME-Version: 1.0
References: <dfc987e3-bb8c-96f5-3bd2-11b9dcc96f19@postgresql.org>
 <CANP8+jLJ_8QjJPxUw2fPO3_zpoym49YeaPmn=wW-rOdZBfsCnQ@mail.gmail.com>
 <3ca94236-9407-b8e8-d632-6fcff1ab5ed8@postgresql.org>
In-Reply-To: <3ca94236-9407-b8e8-d632-6fcff1ab5ed8@postgresql.org>
From: Magnus Hagander <magnus@hagander.net>
Date: Sat, 29 Aug 2020 18:13:49 +0200
Message-ID: 
 <CABUevExeWYLc94bFbNzmdLpHmC3V_CJupev6fUGfYCk3M9iO+A@mail.gmail.com>
Subject: Re: PostgreSQL 13 press release draft
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Cc: Simon Riggs <simon@2ndquadrant.com>,
	PostgreSQL Advocacy <pgsql-advocacy@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000002774b105ae067585"
Precedence: bulk

--0000000000002774b105ae067585
Content-Type: text/plain; charset="UTF-8"

On Sat, Aug 29, 2020 at 5:21 PM Jonathan S. Katz <jkatz@postgresql.org>
wrote:

> On 8/17/20 3:31 PM, Simon Riggs wrote:
> > On Mon, 17 Aug 2020 at 17:07, Jonathan S. Katz <jkatz@postgresql.org>
> wrote:
> >
> >> * The press kit has been slimmed down. This is due to an overall
> >> decrease in actual traffic to the press release through the years,
> >> though downloads themselves have gone up after the release! This likely
> >> due to fragmentation of how people consume PostgreSQL news, as today the
> >> release serves more as a "hey the new PostgreSQL software is available!"
> >
> > It's also because this information is no longer available after
> > release, we just show them directly to the more detailed release
> > notes.
>
> Well, the numbers are much lower even when it is "news" -- that's the
> period I typically measure.
>
> >
> > That's a shame because there is lots of good work in the release
> announcement.
>
> Before I helped to write these, I used to refer to them a lot to
> actually understand what was in a release :)
>
> To your point, perhaps we can make it a bit more visible / accessible on
> the website. The presskits themselves are a bit buried after the
> release[1] but perhaps we can rearrange some things to make them more
> visible for longer. It still does not resolve the first problem I
> mention (traffic to press release down even as news...though will still
> take the "downloads up" overall problem. So long as we spread awareness!)
>

Maybe we should link them from the documentation pages, the same way we do
with direct links to the release notes?

-- 
 Magnus Hagander
 Me: https://www.hagander.net/ <http://www.hagander.net/>
 Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

--0000000000002774b105ae067585
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Sat, Aug 29, 2020 at 5:21 PM Jonat=
han S. Katz &lt;<a href=3D"mailto:jkatz@postgresql.org">jkatz@postgresql.or=
g</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>On 8/17/20 3:31 PM, Simon Riggs wrote:<br>
&gt; On Mon, 17 Aug 2020 at 17:07, Jonathan S. Katz &lt;<a href=3D"mailto:j=
katz@postgresql.org" target=3D"_blank">jkatz@postgresql.org</a>&gt; wrote:<=
br>
&gt; <br>
&gt;&gt; * The press kit has been slimmed down. This is due to an overall<b=
r>
&gt;&gt; decrease in actual traffic to the press release through the years,=
<br>
&gt;&gt; though downloads themselves have gone up after the release! This l=
ikely<br>
&gt;&gt; due to fragmentation of how people consume PostgreSQL news, as tod=
ay the<br>
&gt;&gt; release serves more as a &quot;hey the new PostgreSQL software is =
available!&quot;<br>
&gt; <br>
&gt; It&#39;s also because this information is no longer available after<br=
>
&gt; release, we just show them directly to the more detailed release<br>
&gt; notes.<br>
<br>
Well, the numbers are much lower even when it is &quot;news&quot; -- that&#=
39;s the<br>
period I typically measure.<br>
<br>
&gt; <br>
&gt; That&#39;s a shame because there is lots of good work in the release a=
nnouncement.<br>
<br>
Before I helped to write these, I used to refer to them a lot to<br>
actually understand what was in a release :)<br>
<br>
To your point, perhaps we can make it a bit more visible / accessible on<br=
>
the website. The presskits themselves are a bit buried after the<br>
release[1] but perhaps we can rearrange some things to make them more<br>
visible for longer. It still does not resolve the first problem I<br>
mention (traffic to press release down even as news...though will still<br>
take the &quot;downloads up&quot; overall problem. So long as we spread awa=
reness!)<br></blockquote><div><br></div><div>Maybe we should link them from=
 the documentation pages, the same way we do with direct links to the relea=
se notes?=C2=A0</div></div><div><br></div>-- <br><div dir=3D"ltr" class=3D"=
gmail_signature"><div dir=3D"ltr"><div>=C2=A0Magnus Hagander<br>=C2=A0Me: <=
a href=3D"http://www.hagander.net/" target=3D"_blank">https://www.hagander.=
net/</a><br>=C2=A0Work: <a href=3D"http://www.redpill-linpro.com/" target=
=3D"_blank">https://www.redpill-linpro.com/</a></div></div></div></div>

--0000000000002774b105ae067585--