Small note. After making a blog post, it's a good idea to: - Tweet about it, with a link - Post to Hacker News - Post to /r/programming (Reddit) - Post to /r/Database (Reddit) - Post to /r/nosql (Reddit) - Post to /r/CouchDB (Reddit) - Post to the CouchDB Google+ page - Post to the CouchDB Google+ community
And then after all of that, summarise the post in an email, and post it to user@ and dev@. It's often a good idea to include links to all the other social media stuff you did, and politely ask people to help the project out by retweeting, upvoting, and resharing them. I should probably write up a proper guide on this. For the time being, there are some specific instructions int he release procedure, but they are very specific for making a release. cf. https://wiki.apache.org/couchdb/Release_Procedure#Promoting_the_Release On 6 November 2013 19:19, Noah Slater <[email protected]> wrote: > Andy, > > I reckon you should post it, now you're a committer. :) > > Create a ticket here: > > https://issues.apache.org/jira/browse/INFRA > > Give them your name and email and tell them which blog you want adding to. > > Once you're in, post away! > > On 6 November 2013 18:52, Andy Wenk <[email protected]> wrote: >> Hey Dirkjan, >> >> thanks a lot. It is different to my version but I like it ;-) So +1 for >> posting it in the blog >> >> Cheers >> >> Andy >> >> >> On 6 November 2013 18:29, Dirkjan Ochtman <[email protected]> wrote: >> >>> On Wed, Nov 6, 2013 at 2:18 PM, Andy Wenk <[email protected]> wrote: >>> > I would like to push this a little. It would be cool if you take the time >>> > and read the blog post draft and leave your comments (Noah, any chance >>> yet >>> > ?). You know after the release is before the release ;-) >>> >>> I've rewritten your draft a bunch, I hope you agree the current >>> version is better. >>> >>> Cheers, >>> >>> Dirkjan >>> >> >> >> >> -- >> Andy Wenk >> Hamburg - Germany >> RockIt! >> >> http://www.couchdb-buch.de >> http://www.pg-praxisbuch.de >> >> GPG fingerprint: 3B6D 07F8 8732 CD61 D078 EF7A 63BA 495D 0F15 F21F > > > > -- > Noah Slater > https://twitter.com/nslater -- Noah Slater https://twitter.com/nslater
