Return-Path: X-Original-To: apmail-couchdb-marketing-archive@minotaur.apache.org Delivered-To: apmail-couchdb-marketing-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 20E43117FB for ; Fri, 13 Jun 2014 14:11:45 +0000 (UTC) Received: (qmail 56817 invoked by uid 500); 13 Jun 2014 14:11:45 -0000 Delivered-To: apmail-couchdb-marketing-archive@couchdb.apache.org Received: (qmail 56776 invoked by uid 500); 13 Jun 2014 14:11:44 -0000 Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: marketing@couchdb.apache.org Delivered-To: mailing list marketing@couchdb.apache.org Received: (qmail 56766 invoked by uid 99); 13 Jun 2014 14:11:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jun 2014 14:11:44 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [80.244.253.218] (HELO mail.traeumt.net) (80.244.253.218) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jun 2014 14:11:39 +0000 Received: from [10.0.0.16] (91-64-37-180-dynip.superkabel.de [91.64.37.180]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.traeumt.net (Postfix) with ESMTPSA id 4E6E320910 for ; Fri, 13 Jun 2014 16:11:21 +0200 (CEST) From: Jan Lehnardt Content-Type: multipart/signed; boundary="Apple-Mail=_5D4012C2-2C91-4D34-AD63-18EDDF998893"; protocol="application/pgp-signature"; micalg=pgp-sha512 Message-Id: Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Re: [REQUEST] Promote the CouchDB 1.6.0 release Date: Fri, 13 Jun 2014 16:11:16 +0200 References: <7A0D1539-2DB3-4693-8186-113AC4DF0F95@openssl.it> To: marketing@couchdb.apache.org In-Reply-To: X-Mailer: Apple Mail (2.1878.2) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_5D4012C2-2C91-4D34-AD63-18EDDF998893 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On 13 Jun 2014, at 15:45 , Noah Slater wrote: > Perhaps we could improve this by: >=20 > - 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 = part of the =93PR Merge=94 requirement where dev@ and marketing@ can = work together on writing this up. > On 13 June 2014 15:35, Dirkjan Ochtman 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. 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 = release notes. Happy to split it in two with a tl;dr preceding the = longer explanations which then can also go into the docs What=92s New. Best Jan -- >=20 > - Modifying the steps so the note is sent to marketing@ asking for > people to "marketing-ify" the notes you got from CHANGES >=20 > 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. >=20 > (Does it make sense to cross-post the request to dev@ here also?) >=20 > On 13 June 2014 15:35, Dirkjan Ochtman wrote: >> On Fri, Jun 13, 2014 at 3:17 PM, Noah Slater = wrote: >>> Looping in Dirkjan as our active RM. >>>=20 >>> Relevant part of our release procedure: >>>=20 >>> = http://wiki.apache.org/couchdb/Release_Procedure#Preparing_the_Release_Not= es >>>=20 >>> Template release notes: >>>=20 >>> = https://git-wip-us.apache.org/repos/asf?p=3Dcouchdb-admin.git;a=3Dblob_pla= in;f=3Dnotes/template.html;hb=3DHEAD >>>=20 >>> Relevant instruction from the release procedure: >>>=20 >>> "Go through the CHANGES file and copy each section and summary." >>>=20 >>> The RM should then send the following template email: >>>=20 >>> = https://git-wip-us.apache.org/repos/asf?p=3Dcouchdb-admin.git;a=3Dblob_pla= in;f=3Demail/request_notes.txt;hb=3DHEAD >>>=20 >>> Looks like that wasn't sent for 1.6.0. >>=20 >> Right. I kind of merged that into the SCHEDULE email, where I said: >>=20 >>> I will use these release notes: >>>=20 >>> http://www.apache.org/dist/couchdb/notes/1.6.0/ >>>=20 >>> (Let me know if you have any suggestions for improvements.) >>=20 >> 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. >>=20 >> 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. >>=20 >> 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. >>=20 >> Cheers, >>=20 >> Dirkjan >=20 >=20 >=20 > --=20 > Noah Slater > https://twitter.com/nslater --Apple-Mail=_5D4012C2-2C91-4D34-AD63-18EDDF998893 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJTmwaEAAoJENnuAeR4Uq7klOQP/idcDXTGDWcbW17g9gia2jy+ zWJBxUba6/kwNCMX0ZJZ64tYNvvZ9h0oiWMlECPmuvw6yTV5txYaj0/8v1WpXmxk Oy1iSg9qxN0tUs0rJ41/R0bYl6RaCGpgDceX4JaLYLZaZ7LTUpFofGnwD3iO2fAV vLYIcRs3O3M01VraBIYR61hgoBHKGv441wSZPbGTrQzRqD8OMzfg0ar3Lszq5rdZ ej66nTES93oZ9lc+6QatUjDkHw22Br3bb7eXtH4B9wnIqkCg805Mz5dESSHkHZ15 +e/6ef9OBhPfqj5ZMlHltXgSOjrMGGewdzVGwrQcWeL3on1sVEt3sNRo8CiapDwg zhpAuhUNtHzUpk2i9OA3pN1qMVXcC5ubfQUvtwr5o0Ot/+y6op7iWNOsAT61Rlt5 +M+Y0upBfndTkXsyp8lbuvcwXxrvT2RAd2+yHIJ92ORSrPAPp2THzD9a8a9/9I7T OMjjwev15txZ2BI68OvpZIQUPiLVbCQ55OpZXcUokfgdhjmgak4HOw15R1s5V9PX dL9RM842bysfeG5e+1vHbEq+th2hcsFiVi6Xtj5M0waT/DsCjQbfF1OsjygCF1P2 ZAVlsmKGbLJA6XECT8Nd7z+2BuzpwRFxV8MaimAsoOtsfHg5d5WXYcsxGYHmJUnn lFJR6k/YY38oKnwSyGIv =agzs -----END PGP SIGNATURE----- --Apple-Mail=_5D4012C2-2C91-4D34-AD63-18EDDF998893--