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: <CEB54E11-6BBF-4740-BEE7-CC629CD045D4@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>
 <CADA9kr8s6_F7dLpgstGfNHGBY9mts5-NG1BKyjTrKzwGNcA1YA@mail.gmail.com>
 <CAPaJBx7Ug2UmbpgsiYEqBaXK4sL6D8Q=RP-Jn6qyEqCcx6KVkQ@mail.gmail.com>
 <CAPaJBx4jQ5=eHT+=H9rzLuFQDwBntiHMZ8gMhP685ga3-AMXQA@mail.gmail.com>
 <CEB54E11-6BBF-4740-BEE7-CC629CD045D4@apache.org>
From: Andy Wenk <andy@nms.de>
Date: Mon, 16 Jun 2014 10:54:50 +0200
Message-ID: 
 <CADA9kr_BVz3yPwRwvyQGHWc8w+2VWcf7GcoAbC14rd=VjGa69w@mail.gmail.com>
Subject: Re: [REQUEST] Promote the CouchDB 1.6.0 release
To: "marketing@couchdb.apache.org" <marketing@couchdb.apache.org>
Content-Type: multipart/alternative; boundary=001a113a9238e289a604fbf02ffe

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

Hi all,

On 13 June 2014 16:11, Jan Lehnardt <jan@apache.org> wrote:

>
> On 13 Jun 2014, at 15:45 , Noah Slater <nslater@apache.org> wrote:
>
> > Perhaps we could improve this by:
> >
> > - Moving the release notes bit early in the release process
>
> Or even make it a requirement for the release process to start. We can
> always amend it, if there need to be updates. That way we can make it par=
t
> of the =E2=80=9CPR Merge=E2=80=9D requirement where dev@ and marketing@ c=
an work together
> on writing this up.
>

very good idea. I am +1 on this!


> > On 13 June 2014 15:35, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
>
> >> Adding whatever needs adding to the relevant What's New documentation
> >> chapter might be even better, and can be done at any time by anyone.
>

we should also put a "call for updating the What's New documentation" into
the release process. It's just sending a note to dev@.


> That too, of course, and I think it is important to have a friendlier
> document for the press folks that they can copy from right with the relea=
se
> notes. Happy to split it in two with a tl;dr preceding the longer
> explanations which then can also go into the docs What=E2=80=99s New.
>

breaking it into small chunks in the way press folks can copy and paste the
info is very good. This will increase chances that messages will be
included into news :)


> Best
> Jan
> --


Cheers

Andy


>
>
>
> >
> > - Modifying the steps so the note is sent to marketing@ asking for
> > people to "marketing-ify" the notes you got from CHANGES
> >
> > That can run in parallel with the binaries being prepared. If it
> > happens it happens, if it doesn't it doesn't. But at least there's a
> > clear call to action being made to the marketing team.
> >
> > (Does it make sense to cross-post the request to dev@ here also?)
> >
> > On 13 June 2014 15:35, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
> >> On Fri, Jun 13, 2014 at 3:17 PM, Noah Slater <nslater@apache.org>
> wrote:
> >>> Looping in Dirkjan as our active RM.
> >>>
> >>> Relevant part of our release procedure:
> >>>
> >>>
> http://wiki.apache.org/couchdb/Release_Procedure#Preparing_the_Release_No=
tes
> >>>
> >>> Template release notes:
> >>>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=3Dcouchdb-admin.git;a=3Dblob_pl=
ain;f=3Dnotes/template.html;hb=3DHEAD
> >>>
> >>> Relevant instruction from the release procedure:
> >>>
> >>> "Go through the CHANGES file and copy each section and summary."
> >>>
> >>> The RM should then send the following template email:
> >>>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=3Dcouchdb-admin.git;a=3Dblob_pl=
ain;f=3Demail/request_notes.txt;hb=3DHEAD
> >>>
> >>> Looks like that wasn't sent for 1.6.0.
> >>
> >> Right. I kind of merged that into the SCHEDULE email, where I said:
> >>
> >>> I will use these release notes:
> >>>
> >>>  http://www.apache.org/dist/couchdb/notes/1.6.0/
> >>>
> >>> (Let me know if you have any suggestions for improvements.)
> >>
> >> Part of the problem with the current release procedure is that it is
> >> not factored well enough into interrupts that drive the schedule. E.g.
> >> the RM has to prepare candidate, then wait for the vote. After the
> >> vote, call for binaries and wait for those. In this case, the section
> >> of the procedure describing the release notes stuff comes after the
> >> section describing how to prepare binaries (which I generally don't do
> >> as an RM). So it's kind of easy to skip.
> >>
> >> Also, I believe in the past not many people wanted to have much to do
> >> with crafting the release notes (most people IIRC wanted to generate
> >> them automatically from commit messages). I think the current form is
> >> a bit more friendly, so I spend time each release to go over each
> >> commit in the release, pick out things that are slightly more
> >> relevant/noticeable and describe them in a user-friendly way. I'm not
> >> sure what you guys want to add beyond what we have now (or who is
> >> going to spend time to add it), but I think a small prompt that the
> >> release notes have been prepared should be enough to prompt it.
> >>
> >> Adding whatever needs adding to the relevant What's New documentation
> >> chapter might be even better, and can be done at any time by anyone.
> >>
> >> Cheers,
> >>
> >> Dirkjan
> >
> >
> >
> > --
> > Noah Slater
> > https://twitter.com/nslater
>
>


--=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

--001a113a9238e289a604fbf02ffe--