Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: marketing@couchdb.apache.org
Received-SPF: pass (nike.apache.org: local policy)
MIME-Version: 1.0
Reply-To: andy@nms.de
In-Reply-To: <E11AE6D1-F2B7-4CAC-BA98-D59B4BCC6B31@apache.org>
References: 
 <CAKmKYaAEqdz_vYOaMA20at=j_aDBRdxDQaKzyev8eSuTCTyRww@mail.gmail.com>
 <7A0D1539-2DB3-4693-8186-113AC4DF0F95@openssl.it>
 <CAHdjipKEDmay4OzV6Z-8C4=Lt5yVOhhpMwya-yx7cTbvSRsLdw@mail.gmail.com>
 <CAPaJBx7Zfpd=aBuLh7CYxcECaA56ovAM9d28tRb4c5u81htp9g@mail.gmail.com>
 <CAHdjip+HBYozDnv4jEzFg5_UK65av=j_Lt8PzF999trMXjVzjg@mail.gmail.com>
 <CAPaJBx7Kv5f+gufwUNy=FVxVGeeEiuGbwGdK3KTEpq4kN534qA@mail.gmail.com>
 <CAHdjip++0qN2H1aLFCJ3TPdugEh99viiqfk8dJS_03F1a-MYCg@mail.gmail.com>
 <CAPaJBx6YKMYgHGQ=w-sYbsCknh_L+y=1jF70keZW7O7BKPzktg@mail.gmail.com>
 <CAHdjipJs=Dqme-P_Z2sTM1VrPbjV+atdMApjCijSEjCJbJ9+vw@mail.gmail.com>
 <CAPaJBx5tcG3EAH+bD1emb8T_Sqs7psDxdHyiyAjkx95dCtsh9A@mail.gmail.com>
 <CADA9kr-acHJaBhkdy8PQMtme8dpakdSV9c0184xeYh-RB0ZE0w@mail.gmail.com>
 <E11AE6D1-F2B7-4CAC-BA98-D59B4BCC6B31@apache.org>
From: Andy Wenk <andy@nms.de>
Date: Fri, 13 Jun 2014 09:00:37 +0200
Message-ID: 
 <CADA9kr8s6_F7dLpgstGfNHGBY9mts5-NG1BKyjTrKzwGNcA1YA@mail.gmail.com>
Subject: Re: [REQUEST] Promote the CouchDB 1.6.0 release
To: Jan Lehnardt <jan@apache.org>
Cc: "marketing@couchdb.apache.org" <marketing@couchdb.apache.org>
Content-Type: multipart/alternative; boundary=047d7bf1665edf32d104fbb23ddd

--047d7bf1665edf32d104fbb23ddd
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hey Jan,

I am +1 on short, summarising but still explaining release notes. To come
back to the original discussion, we should then also extract the essential
info from the release notes and create a shorter announce note. This can
then be shared e.g on G+ or in the weekly news.

And yes we can :) . This belongs to the marketing folks I guess but will
need also some info from the devs to write it down correctly.

Cheers

Andy

On 12 June 2014 21:12, Jan Lehnardt <jan@apache.org> wrote:

> Another angle on all this:
>
> For 1.2.0 we prepared longer release notes that not only listed the items
> relevant to the release, but also explained what they meant. There is a
> balance to strike between phrasing it so it is useful vs. not breaking it
> down for absolute noobs. Someone who follows CouchDB a little bit should
> understand them. I understand that=E2=80=99s more work, but this is the s=
tuff that
> ends up being quoted, cited and copied nearly verbatim. The more content
> and context we can provide, the better our coverage is. I don=E2=80=99t t=
hink we
> should go full press-release, but it is also worth mentioning what each
> release means in a larger context. E.g. 1.6.0 is a feature release that
> addresses a number of user requests and also bug fixes that we think is
> worth releasing before the big CouchDB 2.0 / BigCouch merge is done.
>
> Is this something this group can take on?
>
> Best
> Jan
> --
>
>
> On 11 Jun 2014, at 21:54 , Andy Wenk <andy@nms.de> wrote:
>
> > jumping in to the discussion ...
> >
> > On 11 June 2014 21:49, Noah Slater <nslater@apache.org> wrote:
> >
> >> On 11 June 2014 19:50, Alexander Shorin <kxepal@gmail.com> wrote:
> >>
> >>> Another good example how to share release news (sorry for google
> >> translate):
> >>>
> >>
> https://translate.google.com/translate?hl=3Den&sl=3Dru&tl=3Den&u=3Dhttp%3=
A%2F%2Fwww.opennet.ru%2Fopennews%2Fart.shtml%3Fnum%3D39981
> >>> In single post you get quick knowledge about CouchDB: what is it, how
> >>> it works, where it uses, and sure what's in release. And it doesn't
> >>> matter what user will read this post: experienced will just skip the
> >>> header and read the changes list, the new /  potential user will meet
> >>> with the project and may get interested in it.
> >>
> >> This is a whole blog post. And we've already written a whole blog post
> >> about the release. It's on our blog. ;)
> >>
> >
> > yes!
> >
> >
> >> What bothers me is the duplication. We've already written about it
> >> once! Just click and read it there.
> >
> >
> >> Would it be unusual to post the blog text in full to Google+? Do
> >> people really expect you to summarise blog posts when you share them
> >> on Google+?
> >>
> >
> > I don't think so. I think people expect a quick summary to scan if the
> > content of the posted link is interesting to read or not. I personally =
do
> > not read longer posts on G+. But what I like is a summary and I think
> this
> > is what Alex is proposing ...
> >
> > Cheers
> >
> > Andy
> >
> >
> >>
> >> --
> >> Noah Slater
> >> https://twitter.com/nslater
> >>
> >
> >
> >
> > --
> > Andy Wenk
> > Hamburg - Germany
> > RockIt!
> >
> > http://www.couchdb-buch.de
> > http://www.pg-praxisbuch.de
> >
> > GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
> >
> > https://people.apache.org/keys/committer/andywenk.asc
>
>


--=20
Andy Wenk
Hamburg - Germany
RockIt!

http://www.couchdb-buch.de
http://www.pg-praxisbuch.de

GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588

https://people.apache.org/keys/committer/andywenk.asc

--047d7bf1665edf32d104fbb23ddd--