You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Dirkjan Ochtman <di...@ochtman.nl> on 2014/06/10 19:32:36 UTC
[REQUEST] Promote the CouchDB 1.6.0 release
Dear community,
Being a volunteer organisation, we rely on you to help us promote releases.
Here is the official blog post:
https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0
Here is the official tweet:
https://twitter.com/CouchDB/status/476414924412178432
We also have a Hacker News item:
https://news.ycombinator.com/item?id=7873968
And several Reddit items:
http://www.reddit.com/r/programming/comments/27svpz/apache_couchdb_160_released/
http://www.reddit.com/r/Database/comments/27svqw/apache_couchdb_160_released/
http://www.reddit.com/r/nosql/comments/27svrx/apache_couchdb_160_released/
http://www.reddit.com/r/CouchDB/comments/27svsk/apache_couchdb_160_released/
Please take a moment to share these links with your friends.
Retweet us if you use Twitter, and upvote us if you use Hacker News, or Reddit.
(Note that Hacker News users may want to navigate to the item from the
front page. I believe up votes are not counted when you link to an
item directly.)
If you are active on Google+, Lobste.rs, or other relevant social
media, please share the news there and report back on this thread.
If you like, you could monitor these threads and respond to people
with questions. This is a great opportunity for community outreach.
If you have any other promotion you'd like to highlight, please reply
to this thread.
Thanks,
Dirkjan
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Andy Wenk <an...@nms.de>.
Hi Dirkjan,
thanks a lot for the release. We waited really long this time - but finally
we did it. thanks to all contributors in the CouchDB universe. Let's no
rock the next release!
Cheers
Andy
On 10 June 2014 19:32, Dirkjan Ochtman <di...@ochtman.nl> wrote:
> Dear community,
>
> Being a volunteer organisation, we rely on you to help us promote releases.
>
> Here is the official blog post:
>
> https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0
>
> Here is the official tweet:
>
> https://twitter.com/CouchDB/status/476414924412178432
>
> We also have a Hacker News item:
>
> https://news.ycombinator.com/item?id=7873968
>
> And several Reddit items:
>
>
> http://www.reddit.com/r/programming/comments/27svpz/apache_couchdb_160_released/
>
> http://www.reddit.com/r/Database/comments/27svqw/apache_couchdb_160_released/
>
> http://www.reddit.com/r/nosql/comments/27svrx/apache_couchdb_160_released/
>
> http://www.reddit.com/r/CouchDB/comments/27svsk/apache_couchdb_160_released/
>
> Please take a moment to share these links with your friends.
>
> Retweet us if you use Twitter, and upvote us if you use Hacker News, or
> Reddit.
>
> (Note that Hacker News users may want to navigate to the item from the
> front page. I believe up votes are not counted when you link to an
> item directly.)
>
> If you are active on Google+, Lobste.rs, or other relevant social
> media, please share the news there and report back on this thread.
>
> If you like, you could monitor these threads and respond to people
> with questions. This is a great opportunity for community outreach.
>
> If you have any other promotion you'd like to highlight, please reply
> to this thread.
>
> Thanks,
>
> Dirkjan
>
--
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
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Andy Wenk <an...@nms.de>.
Hi Dirkjan,
thanks a lot for the release. We waited really long this time - but finally
we did it. thanks to all contributors in the CouchDB universe. Let's no
rock the next release!
Cheers
Andy
On 10 June 2014 19:32, Dirkjan Ochtman <di...@ochtman.nl> wrote:
> Dear community,
>
> Being a volunteer organisation, we rely on you to help us promote releases.
>
> Here is the official blog post:
>
> https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0
>
> Here is the official tweet:
>
> https://twitter.com/CouchDB/status/476414924412178432
>
> We also have a Hacker News item:
>
> https://news.ycombinator.com/item?id=7873968
>
> And several Reddit items:
>
>
> http://www.reddit.com/r/programming/comments/27svpz/apache_couchdb_160_released/
>
> http://www.reddit.com/r/Database/comments/27svqw/apache_couchdb_160_released/
>
> http://www.reddit.com/r/nosql/comments/27svrx/apache_couchdb_160_released/
>
> http://www.reddit.com/r/CouchDB/comments/27svsk/apache_couchdb_160_released/
>
> Please take a moment to share these links with your friends.
>
> Retweet us if you use Twitter, and upvote us if you use Hacker News, or
> Reddit.
>
> (Note that Hacker News users may want to navigate to the item from the
> front page. I believe up votes are not counted when you link to an
> item directly.)
>
> If you are active on Google+, Lobste.rs, or other relevant social
> media, please share the news there and report back on this thread.
>
> If you like, you could monitor these threads and respond to people
> with questions. This is a great opportunity for community outreach.
>
> If you have any other promotion you'd like to highlight, please reply
> to this thread.
>
> Thanks,
>
> Dirkjan
>
--
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
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Andy Wenk <an...@nms.de>.
Hi all,
On 13 June 2014 16:11, Jan Lehnardt <ja...@apache.org> wrote:
>
> On 13 Jun 2014, at 15:45 , Noah Slater <ns...@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 part
> of the “PR Merge” requirement where dev@ and marketing@ can work together
> on writing this up.
>
very good idea. I am +1 on this!
> > On 13 June 2014 15:35, Dirkjan Ochtman <di...@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 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’s 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 <di...@ochtman.nl> wrote:
> >> On Fri, Jun 13, 2014 at 3:17 PM, Noah Slater <ns...@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_Notes
> >>>
> >>> Template release notes:
> >>>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=couchdb-admin.git;a=blob_plain;f=notes/template.html;hb=HEAD
> >>>
> >>> 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=couchdb-admin.git;a=blob_plain;f=email/request_notes.txt;hb=HEAD
> >>>
> >>> 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
>
>
--
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
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Jan Lehnardt <ja...@apache.org>.
On 13 Jun 2014, at 15:45 , Noah Slater <ns...@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 part of the “PR Merge” requirement where dev@ and marketing@ can work together on writing this up.
> On 13 June 2014 15:35, Dirkjan Ochtman <di...@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.
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’s New.
Best
Jan
--
>
> - 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 <di...@ochtman.nl> wrote:
>> On Fri, Jun 13, 2014 at 3:17 PM, Noah Slater <ns...@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_Notes
>>>
>>> Template release notes:
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=couchdb-admin.git;a=blob_plain;f=notes/template.html;hb=HEAD
>>>
>>> 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=couchdb-admin.git;a=blob_plain;f=email/request_notes.txt;hb=HEAD
>>>
>>> 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
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Noah Slater <ns...@apache.org>.
Perhaps we could improve this by:
- Moving the release notes bit early in the release process
- 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 <di...@ochtman.nl> wrote:
> On Fri, Jun 13, 2014 at 3:17 PM, Noah Slater <ns...@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_Notes
>>
>> Template release notes:
>>
>> https://git-wip-us.apache.org/repos/asf?p=couchdb-admin.git;a=blob_plain;f=notes/template.html;hb=HEAD
>>
>> 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=couchdb-admin.git;a=blob_plain;f=email/request_notes.txt;hb=HEAD
>>
>> 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
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Dirkjan Ochtman <di...@ochtman.nl>.
On Fri, Jun 13, 2014 at 3:17 PM, Noah Slater <ns...@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_Notes
>
> Template release notes:
>
> https://git-wip-us.apache.org/repos/asf?p=couchdb-admin.git;a=blob_plain;f=notes/template.html;hb=HEAD
>
> 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=couchdb-admin.git;a=blob_plain;f=email/request_notes.txt;hb=HEAD
>
> 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
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Noah Slater <ns...@apache.org>.
Looping in Dirkjan as our active RM.
Relevant part of our release procedure:
http://wiki.apache.org/couchdb/Release_Procedure#Preparing_the_Release_Notes
Template release notes:
https://git-wip-us.apache.org/repos/asf?p=couchdb-admin.git;a=blob_plain;f=notes/template.html;hb=HEAD
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=couchdb-admin.git;a=blob_plain;f=email/request_notes.txt;hb=HEAD
Looks like that wasn't sent for 1.6.0.
If we made sure to do this for future releases, do you think this
satisfies your request Jan?
On 13 June 2014 09:00, Andy Wenk <an...@nms.de> wrote:
> 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 <ja...@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’s more work, but this is the stuff 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’t think 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 <an...@nms.de> wrote:
>>
>> > jumping in to the discussion ...
>> >
>> > On 11 June 2014 21:49, Noah Slater <ns...@apache.org> wrote:
>> >
>> >> On 11 June 2014 19:50, Alexander Shorin <kx...@gmail.com> wrote:
>> >>
>> >>> Another good example how to share release news (sorry for google
>> >> translate):
>> >>>
>> >>
>> https://translate.google.com/translate?hl=en&sl=ru&tl=en&u=http%3A%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
>>
>>
>
>
> --
> 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
--
Noah Slater
https://twitter.com/nslater
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Andy Wenk <an...@nms.de>.
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 <ja...@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’s more work, but this is the stuff 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’t think 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 <an...@nms.de> wrote:
>
> > jumping in to the discussion ...
> >
> > On 11 June 2014 21:49, Noah Slater <ns...@apache.org> wrote:
> >
> >> On 11 June 2014 19:50, Alexander Shorin <kx...@gmail.com> wrote:
> >>
> >>> Another good example how to share release news (sorry for google
> >> translate):
> >>>
> >>
> https://translate.google.com/translate?hl=en&sl=ru&tl=en&u=http%3A%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
>
>
--
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
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Jan Lehnardt <ja...@apache.org>.
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’s more work, but this is the stuff 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’t think 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 <an...@nms.de> wrote:
> jumping in to the discussion ...
>
> On 11 June 2014 21:49, Noah Slater <ns...@apache.org> wrote:
>
>> On 11 June 2014 19:50, Alexander Shorin <kx...@gmail.com> wrote:
>>
>>> Another good example how to share release news (sorry for google
>> translate):
>>>
>> https://translate.google.com/translate?hl=en&sl=ru&tl=en&u=http%3A%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
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Andy Wenk <an...@nms.de>.
jumping in to the discussion ...
On 11 June 2014 21:49, Noah Slater <ns...@apache.org> wrote:
> On 11 June 2014 19:50, Alexander Shorin <kx...@gmail.com> wrote:
>
> > Another good example how to share release news (sorry for google
> translate):
> >
> https://translate.google.com/translate?hl=en&sl=ru&tl=en&u=http%3A%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
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Alexander Shorin <kx...@gmail.com>.
On Wed, Jun 11, 2014 at 11:49 PM, Noah Slater <ns...@apache.org> wrote:
> On 11 June 2014 19:50, Alexander Shorin <kx...@gmail.com> wrote:
>
>> Another good example how to share release news (sorry for google translate):
>> https://translate.google.com/translate?hl=en&sl=ru&tl=en&u=http%3A%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. ;)
>
> 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+?
Hm....Really, this is mostly about blog post, you're. I eventually
moved from statement of being "a bit more verbose" to "be verbose" in
my thoughts (: As for G+/FB news first is better.
--
,,,^..^,,,
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Noah Slater <ns...@apache.org>.
On 11 June 2014 19:50, Alexander Shorin <kx...@gmail.com> wrote:
> Another good example how to share release news (sorry for google translate):
> https://translate.google.com/translate?hl=en&sl=ru&tl=en&u=http%3A%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. ;)
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+?
--
Noah Slater
https://twitter.com/nslater
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Alexander Shorin <kx...@gmail.com>.
On Wed, Jun 11, 2014 at 9:22 PM, Noah Slater <ns...@apache.org> wrote:
> On 11 June 2014 16:43, Alexander Shorin <kx...@gmail.com> wrote:
>
>> Under "non-interesting" I mean the news as like as ours. "Foo get
>> release X.Y.Z. This is feature release". "Okay " is the only reaction
>> of users who are not directly related to "Foo" project and obliviously
>> such news wouldn't raise any interest from their side.
>
> Not sure why people would be following CouchDB if they didn't care
> about our releases. Perhaps I'm missing something?
People from extended circles of those who follows CouchDB and shares
their posts with are "potential followers" and they may get interested
and follow CouchDB (and become CouchDB user in future). For the same
reasons I follow various databases and projects: while I'm not their
active user I like to read interesting stuff they share.
Why care about our releases news? Because our releases is the best way
to promote our features again and again and show how they becomes
better in time without blame for noise generation or for aggressive
marketing. Say, you don't know anything about CouchDB and see "Apache
CouchDB 1.6.0 released" topic. Currently the situation will be: "Ok,
released, congrats, moving on". With few notices about release as
Marcello did you'll more likely read about changes and notice project
features. Since that point you may get interested, click on link and
read more about or moving on. But you'll left with some more knowledge
about CouchDB than in case of "this is a feature release".
Another good example how to share release news (sorry for google translate):
https://translate.google.com/translate?hl=en&sl=ru&tl=en&u=http%3A%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.
>> As a good example I could recommend this "community" (better call it
>> G+ news feed of single man):
>
> The third post down is this:
>
> https://plus.google.com/110423559145794735162/posts/WCnwykhcyy8
>
> someone is sharing the weekly news, with the only comment being:
>
> "A little bit late ;)"
Yeap, and would you click on such link? (; Probably, you'll skip it
without being noticed.
--
,,,^..^,,,
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Noah Slater <ns...@apache.org>.
On 11 June 2014 16:43, Alexander Shorin <kx...@gmail.com> wrote:
> Under "non-interesting" I mean the news as like as ours. "Foo get
> release X.Y.Z. This is feature release". "Okay " is the only reaction
> of users who are not directly related to "Foo" project and obliviously
> such news wouldn't raise any interest from their side.
Not sure why people would be following CouchDB if they didn't care
about our releases. Perhaps I'm missing something?
> HN for this release is not very active ):
HN is a crapshoot, unfortunately. (That's a gambling term.)
> As a good example I could recommend this "community" (better call it
> G+ news feed of single man):
The third post down is this:
https://plus.google.com/110423559145794735162/posts/WCnwykhcyy8
someone is sharing the weekly news, with the only comment being:
"A little bit late ;)"
> Ok, but I could only handle G+ channel - don't have an account and not
> plan to sign up to FB. However, as for preparing summaries this could
> be done here at marketing@ right before release would be announced.
Okay cool. Would be good to do it for weekly news too pls!
I can use your summaries when posting to FB.
--
Noah Slater
https://twitter.com/nslater
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Alexander Shorin <kx...@gmail.com>.
On Wed, Jun 11, 2014 at 6:22 PM, Noah Slater <ns...@apache.org> wrote:
> On 11 June 2014 15:52, Alexander Shorin <kx...@gmail.com> wrote:
>> Another problem is that as more non-interesting news
>> we sharing as more likely these posts will be ignored
>
> Can you clarify this point? What "non-interesting" news?
When you continuously receive non-interesting news from single source
which you're not directly subscribed what is your the most probably
action? You'll mute such posts (actively via social network ignore
system or passively as like as we're all ignoring any advertisement
blocks on websites).
Under "non-interesting" I mean the news as like as ours. "Foo get
release X.Y.Z. This is feature release". "Okay " is the only reaction
of users who are not directly related to "Foo" project and obliviously
such news wouldn't raise any interest from their side.
>> Marketing isn't only about
>> managing existed community, but also is about attracting new members.
>
> Agreed. However, my time and attention is limited, so I need to be
> careful where I spend it. :) One way of prioritising is pursuing the
> channels that get us the most exposure. At the moment, that's Twitter,
> Hacker News, and Reddit. Everything else is secondary.
HN for this release is not very active ):
>> There is no need use analytics and pageviews to guess that with single
>> dry sentences it's merely hard to rich this goal...
>
> I agree. But producing the summaries takes time, which again, is my
> only limited resource. :) I was looking through my Google+ feed today
> (for the first time in several years) and I noticed that many people
> share links without any description whatsoever.
And that's a pity ): Sometimes I do the same when I have nothing to
add or just share-to-bookmark for myself.
As a good example I could recommend this "community" (better call it
G+ news feed of single man):
https://plus.google.com/communities/111792909020617121355
Almost every shared link preluded with short description about if it
was missed in <meta> tags or contains non-attractive title. If not
these annotations, I would probably ignore most of these posts missing
some interesting ones.
>> ...but wait, I don't wear marketing hat (:
>
> Sure you do. You're on the list, you're on the marketing team. :)
Ouch... ((:
>>> If you're like to help, that'd be sweet.
>>
>> How?
>
> Perhaps by writing these summaries and posting them to both Google+
> and Facebook, and also taking over the management of both of these
> channels, working to grow and nurture the communities there.
> Interested?
Ok, but I could only handle G+ channel - don't have an account and not
plan to sign up to FB. However, as for preparing summaries this could
be done here at marketing@ right before release would be announced.
--
,,,^..^,,,
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Noah Slater <ns...@apache.org>.
On 11 June 2014 15:52, Alexander Shorin <kx...@gmail.com> wrote:
> Another problem is that as more non-interesting news
> we sharing as more likely these posts will be ignored
Can you clarify this point? What "non-interesting" news?
> Marketing isn't only about
> managing existed community, but also is about attracting new members.
Agreed. However, my time and attention is limited, so I need to be
careful where I spend it. :) One way of prioritising is pursuing the
channels that get us the most exposure. At the moment, that's Twitter,
Hacker News, and Reddit. Everything else is secondary.
> There is no need use analytics and pageviews to guess that with single
> dry sentences it's merely hard to rich this goal...
I agree. But producing the summaries takes time, which again, is my
only limited resource. :) I was looking through my Google+ feed today
(for the first time in several years) and I noticed that many people
share links without any description whatsoever.
> ...but wait, I don't wear marketing hat (:
Sure you do. You're on the list, you're on the marketing team. :)
>> If you're like to help, that'd be sweet.
>
> How?
Perhaps by writing these summaries and posting them to both Google+
and Facebook, and also taking over the management of both of these
channels, working to grow and nurture the communities there.
Interested?
Thanks!
--
Noah Slater
https://twitter.com/nslater
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Alexander Shorin <kx...@gmail.com>.
Not only G+, Facebook too. (;
As for G+: at least 457 community + 158 page subscribers for direct
receiving the release news + 4710 potential users who received post
via sharing (currently 5 reshares done). That's about closely to a
half of twitter subscribers. However, these potential users will
navigate to our blog only in single case: the post has nice and
attractive title (otherwise they would subscribe directly to our
page/community). Another problem is that as more non-interesting news
we sharing as more likely these posts will be ignored, so with every
post we decreasing chances that these people will navigate to our
blog. Don't know how large our FB community is, but anyway I don't
think we're ever in place to choose. Marketing isn't only about
managing existed community, but also is about attracting new members.
There is no need use analytics and pageviews to guess that with single
dry sentences it's merely hard to rich this goal...
...but wait, I don't wear marketing hat (:
> If you're like to help, that'd be sweet.
How?
--
,,,^..^,,,
On Wed, Jun 11, 2014 at 3:29 PM, Noah Slater <ns...@apache.org> wrote:
> I don't think that many people use Google+, so it's not high on my
> list of things to spend time on when doing promotional work. If you're
> like to help, that'd be sweet. Once we get the analytics sorted out on
> our blog, we'll be able to see just how many pageviews its driving and
> we can experiment with formats to see if we can increase those.
>
>
> On 10 June 2014 22:41, Alexander Shorin <kx...@gmail.com> wrote:
>> On Wed, Jun 11, 2014 at 12:35 AM, Marcello Barnaba <vj...@openssl.it> wrote:
>>> On 10 Jun 2014, at 19:32, Dirkjan Ochtman <di...@ochtman.nl> wrote:
>>>
>>>> Dear community,
>>>>
>>>> Being a volunteer organisation, we rely on you to help us promote releases.
>>> []
>>>> If you are active on Google+, Lobste.rs, or other relevant social
>>>> media, please share the news there and report back on this thread.
>>>
>>>
>>> I’ve shared a post on G+, both with the Public circle and interested peers:
>>>
>>> https://plus.google.com/u/0/+MarcelloBarnaba/posts/PPyHsqQdTdp
>>
>> Thanks, Marcello!
>>
>> This is how we should share news about our releases. Not with just
>> "This is a feature release" phrase of nothing (;
>>
>> --
>> ,,,^..^,,,
>
>
>
> --
> Noah Slater
> https://twitter.com/nslater
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Noah Slater <ns...@apache.org>.
I don't think that many people use Google+, so it's not high on my
list of things to spend time on when doing promotional work. If you're
like to help, that'd be sweet. Once we get the analytics sorted out on
our blog, we'll be able to see just how many pageviews its driving and
we can experiment with formats to see if we can increase those.
On 10 June 2014 22:41, Alexander Shorin <kx...@gmail.com> wrote:
> On Wed, Jun 11, 2014 at 12:35 AM, Marcello Barnaba <vj...@openssl.it> wrote:
>> On 10 Jun 2014, at 19:32, Dirkjan Ochtman <di...@ochtman.nl> wrote:
>>
>>> Dear community,
>>>
>>> Being a volunteer organisation, we rely on you to help us promote releases.
>> []
>>> If you are active on Google+, Lobste.rs, or other relevant social
>>> media, please share the news there and report back on this thread.
>>
>>
>> I’ve shared a post on G+, both with the Public circle and interested peers:
>>
>> https://plus.google.com/u/0/+MarcelloBarnaba/posts/PPyHsqQdTdp
>
> Thanks, Marcello!
>
> This is how we should share news about our releases. Not with just
> "This is a feature release" phrase of nothing (;
>
> --
> ,,,^..^,,,
--
Noah Slater
https://twitter.com/nslater
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Alexander Shorin <kx...@gmail.com>.
On Wed, Jun 11, 2014 at 12:35 AM, Marcello Barnaba <vj...@openssl.it> wrote:
> On 10 Jun 2014, at 19:32, Dirkjan Ochtman <di...@ochtman.nl> wrote:
>
>> Dear community,
>>
>> Being a volunteer organisation, we rely on you to help us promote releases.
> []
>> If you are active on Google+, Lobste.rs, or other relevant social
>> media, please share the news there and report back on this thread.
>
>
> I’ve shared a post on G+, both with the Public circle and interested peers:
>
> https://plus.google.com/u/0/+MarcelloBarnaba/posts/PPyHsqQdTdp
Thanks, Marcello!
This is how we should share news about our releases. Not with just
"This is a feature release" phrase of nothing (;
--
,,,^..^,,,
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Marcello Barnaba <vj...@openssl.it>.
Hi Dirkjan,
On 10 Jun 2014, at 19:32, Dirkjan Ochtman <di...@ochtman.nl> wrote:
> Dear community,
>
> Being a volunteer organisation, we rely on you to help us promote releases.
[]
> If you are active on Google+, Lobste.rs, or other relevant social
> media, please share the news there and report back on this thread.
I’ve shared a post on G+, both with the Public circle and interested peers:
https://plus.google.com/u/0/+MarcelloBarnaba/posts/PPyHsqQdTdp
I summed up what I felt relevant from the release notes on the blog post,
from my perspective. :-)
Cheers,
~Marcello
--
~ vjt@openssl.it
~ http://sindro.me
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Noah Slater <ns...@apache.org>.
Thanks so much Dirkjan. Here are the other links:
https://plus.google.com/+CouchDB/posts/fVZ8EJ1aWBE
https://www.facebook.com/permalink.php?story_fbid=544286788936883&id=507603582605204
https://lobste.rs/s/nu8sf5/apache_couchdb_1_6_0_released
Please, please help us to promote. It really helps us get the news
out, which in turn helps us to grow the community, and improve the
project. This is a super easy way to get involved and contribute to
the project. Every bit of help is massively appreciated!
Thank you!
On 10 June 2014 19:32, Dirkjan Ochtman <di...@ochtman.nl> wrote:
> Dear community,
>
> Being a volunteer organisation, we rely on you to help us promote releases.
>
> Here is the official blog post:
>
> https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0
>
> Here is the official tweet:
>
> https://twitter.com/CouchDB/status/476414924412178432
>
> We also have a Hacker News item:
>
> https://news.ycombinator.com/item?id=7873968
>
> And several Reddit items:
>
> http://www.reddit.com/r/programming/comments/27svpz/apache_couchdb_160_released/
> http://www.reddit.com/r/Database/comments/27svqw/apache_couchdb_160_released/
> http://www.reddit.com/r/nosql/comments/27svrx/apache_couchdb_160_released/
> http://www.reddit.com/r/CouchDB/comments/27svsk/apache_couchdb_160_released/
>
> Please take a moment to share these links with your friends.
>
> Retweet us if you use Twitter, and upvote us if you use Hacker News, or Reddit.
>
> (Note that Hacker News users may want to navigate to the item from the
> front page. I believe up votes are not counted when you link to an
> item directly.)
>
> If you are active on Google+, Lobste.rs, or other relevant social
> media, please share the news there and report back on this thread.
>
> If you like, you could monitor these threads and respond to people
> with questions. This is a great opportunity for community outreach.
>
> If you have any other promotion you'd like to highlight, please reply
> to this thread.
>
> Thanks,
>
> Dirkjan
--
Noah Slater
https://twitter.com/nslater
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Noah Slater <ns...@apache.org>.
Thanks so much Dirkjan. Here are the other links:
https://plus.google.com/+CouchDB/posts/fVZ8EJ1aWBE
https://www.facebook.com/permalink.php?story_fbid=544286788936883&id=507603582605204
https://lobste.rs/s/nu8sf5/apache_couchdb_1_6_0_released
Please, please help us to promote. It really helps us get the news
out, which in turn helps us to grow the community, and improve the
project. This is a super easy way to get involved and contribute to
the project. Every bit of help is massively appreciated!
Thank you!
On 10 June 2014 19:32, Dirkjan Ochtman <di...@ochtman.nl> wrote:
> Dear community,
>
> Being a volunteer organisation, we rely on you to help us promote releases.
>
> Here is the official blog post:
>
> https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0
>
> Here is the official tweet:
>
> https://twitter.com/CouchDB/status/476414924412178432
>
> We also have a Hacker News item:
>
> https://news.ycombinator.com/item?id=7873968
>
> And several Reddit items:
>
> http://www.reddit.com/r/programming/comments/27svpz/apache_couchdb_160_released/
> http://www.reddit.com/r/Database/comments/27svqw/apache_couchdb_160_released/
> http://www.reddit.com/r/nosql/comments/27svrx/apache_couchdb_160_released/
> http://www.reddit.com/r/CouchDB/comments/27svsk/apache_couchdb_160_released/
>
> Please take a moment to share these links with your friends.
>
> Retweet us if you use Twitter, and upvote us if you use Hacker News, or Reddit.
>
> (Note that Hacker News users may want to navigate to the item from the
> front page. I believe up votes are not counted when you link to an
> item directly.)
>
> If you are active on Google+, Lobste.rs, or other relevant social
> media, please share the news there and report back on this thread.
>
> If you like, you could monitor these threads and respond to people
> with questions. This is a great opportunity for community outreach.
>
> If you have any other promotion you'd like to highlight, please reply
> to this thread.
>
> Thanks,
>
> Dirkjan
--
Noah Slater
https://twitter.com/nslater
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Andy Wenk <an...@nms.de>.
Hi Dirkjan,
thanks a lot for the release. We waited really long this time - but finally
we did it. thanks to all contributors in the CouchDB universe. Let's no
rock the next release!
Cheers
Andy
On 10 June 2014 19:32, Dirkjan Ochtman <di...@ochtman.nl> wrote:
> Dear community,
>
> Being a volunteer organisation, we rely on you to help us promote releases.
>
> Here is the official blog post:
>
> https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0
>
> Here is the official tweet:
>
> https://twitter.com/CouchDB/status/476414924412178432
>
> We also have a Hacker News item:
>
> https://news.ycombinator.com/item?id=7873968
>
> And several Reddit items:
>
>
> http://www.reddit.com/r/programming/comments/27svpz/apache_couchdb_160_released/
>
> http://www.reddit.com/r/Database/comments/27svqw/apache_couchdb_160_released/
>
> http://www.reddit.com/r/nosql/comments/27svrx/apache_couchdb_160_released/
>
> http://www.reddit.com/r/CouchDB/comments/27svsk/apache_couchdb_160_released/
>
> Please take a moment to share these links with your friends.
>
> Retweet us if you use Twitter, and upvote us if you use Hacker News, or
> Reddit.
>
> (Note that Hacker News users may want to navigate to the item from the
> front page. I believe up votes are not counted when you link to an
> item directly.)
>
> If you are active on Google+, Lobste.rs, or other relevant social
> media, please share the news there and report back on this thread.
>
> If you like, you could monitor these threads and respond to people
> with questions. This is a great opportunity for community outreach.
>
> If you have any other promotion you'd like to highlight, please reply
> to this thread.
>
> Thanks,
>
> Dirkjan
>
--
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
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Noah Slater <ns...@apache.org>.
Nice!
On 11 June 2014 23:10, Jan Lehnardt <ja...@apache.org> wrote:
> marketing@ only:
>
> Yay, we mate the SD times! http://www.sdtimes.com/content/article.aspx?ArticleID=71368&page=1 :)
>
> Best
> Jan
> --
>
> On 10 Jun 2014, at 19:32 , Dirkjan Ochtman <di...@ochtman.nl> wrote:
>
>> Dear community,
>>
>> Being a volunteer organisation, we rely on you to help us promote releases.
>>
>> Here is the official blog post:
>>
>> https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0
>>
>> Here is the official tweet:
>>
>> https://twitter.com/CouchDB/status/476414924412178432
>>
>> We also have a Hacker News item:
>>
>> https://news.ycombinator.com/item?id=7873968
>>
>> And several Reddit items:
>>
>> http://www.reddit.com/r/programming/comments/27svpz/apache_couchdb_160_released/
>> http://www.reddit.com/r/Database/comments/27svqw/apache_couchdb_160_released/
>> http://www.reddit.com/r/nosql/comments/27svrx/apache_couchdb_160_released/
>> http://www.reddit.com/r/CouchDB/comments/27svsk/apache_couchdb_160_released/
>>
>> Please take a moment to share these links with your friends.
>>
>> Retweet us if you use Twitter, and upvote us if you use Hacker News, or Reddit.
>>
>> (Note that Hacker News users may want to navigate to the item from the
>> front page. I believe up votes are not counted when you link to an
>> item directly.)
>>
>> If you are active on Google+, Lobste.rs, or other relevant social
>> media, please share the news there and report back on this thread.
>>
>> If you like, you could monitor these threads and respond to people
>> with questions. This is a great opportunity for community outreach.
>>
>> If you have any other promotion you'd like to highlight, please reply
>> to this thread.
>>
>> Thanks,
>>
>> Dirkjan
>
--
Noah Slater
https://twitter.com/nslater
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Jan Lehnardt <ja...@apache.org>.
marketing@ only:
Yay, we mate the SD times! http://www.sdtimes.com/content/article.aspx?ArticleID=71368&page=1 :)
Best
Jan
--
On 10 Jun 2014, at 19:32 , Dirkjan Ochtman <di...@ochtman.nl> wrote:
> Dear community,
>
> Being a volunteer organisation, we rely on you to help us promote releases.
>
> Here is the official blog post:
>
> https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0
>
> Here is the official tweet:
>
> https://twitter.com/CouchDB/status/476414924412178432
>
> We also have a Hacker News item:
>
> https://news.ycombinator.com/item?id=7873968
>
> And several Reddit items:
>
> http://www.reddit.com/r/programming/comments/27svpz/apache_couchdb_160_released/
> http://www.reddit.com/r/Database/comments/27svqw/apache_couchdb_160_released/
> http://www.reddit.com/r/nosql/comments/27svrx/apache_couchdb_160_released/
> http://www.reddit.com/r/CouchDB/comments/27svsk/apache_couchdb_160_released/
>
> Please take a moment to share these links with your friends.
>
> Retweet us if you use Twitter, and upvote us if you use Hacker News, or Reddit.
>
> (Note that Hacker News users may want to navigate to the item from the
> front page. I believe up votes are not counted when you link to an
> item directly.)
>
> If you are active on Google+, Lobste.rs, or other relevant social
> media, please share the news there and report back on this thread.
>
> If you like, you could monitor these threads and respond to people
> with questions. This is a great opportunity for community outreach.
>
> If you have any other promotion you'd like to highlight, please reply
> to this thread.
>
> Thanks,
>
> Dirkjan
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Marcello Barnaba <vj...@openssl.it>.
Hi Dirkjan,
On 10 Jun 2014, at 19:32, Dirkjan Ochtman <di...@ochtman.nl> wrote:
> Dear community,
>
> Being a volunteer organisation, we rely on you to help us promote releases.
[]
> If you are active on Google+, Lobste.rs, or other relevant social
> media, please share the news there and report back on this thread.
I’ve shared a post on G+, both with the Public circle and interested peers:
https://plus.google.com/u/0/+MarcelloBarnaba/posts/PPyHsqQdTdp
I summed up what I felt relevant from the release notes on the blog post,
from my perspective. :-)
Cheers,
~Marcello
--
~ vjt@openssl.it
~ http://sindro.me
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Marcello Barnaba <vj...@openssl.it>.
Hi Dirkjan,
On 10 Jun 2014, at 19:32, Dirkjan Ochtman <di...@ochtman.nl> wrote:
> Dear community,
>
> Being a volunteer organisation, we rely on you to help us promote releases.
[]
> If you are active on Google+, Lobste.rs, or other relevant social
> media, please share the news there and report back on this thread.
I’ve shared a post on G+, both with the Public circle and interested peers:
https://plus.google.com/u/0/+MarcelloBarnaba/posts/PPyHsqQdTdp
I summed up what I felt relevant from the release notes on the blog post,
from my perspective. :-)
Cheers,
~Marcello
--
~ vjt@openssl.it
~ http://sindro.me
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Peter Cooper <pe...@cooperpress.com>.
Absolutely, thanks!
On Tue, Jun 10, 2014 at 10:46 PM, Andy Wenk <an...@apache.org> wrote:
> Hi Peter,
>
> I just want to make sure, you don't miss the great news about the Apache
> CouchDB 1.6.0 release :).
>
> All the best
>
> Andy
>
> ---------- Forwarded message ----------
> From: Dirkjan Ochtman <di...@ochtman.nl>
> Date: 10 June 2014 19:32
> Subject: [REQUEST] Promote the CouchDB 1.6.0 release
> To: "dev@couchdb.apache.org" <de...@couchdb.apache.org>, "
> user@couchdb.apache.org" <us...@couchdb.apache.org>,
> marketing@couchdb.apache.org
>
>
> Dear community,
>
> Being a volunteer organisation, we rely on you to help us promote releases.
>
> Here is the official blog post:
>
> https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0
>
> Here is the official tweet:
>
> https://twitter.com/CouchDB/status/476414924412178432
>
> We also have a Hacker News item:
>
> https://news.ycombinator.com/item?id=7873968
>
> And several Reddit items:
>
>
> http://www.reddit.com/r/programming/comments/27svpz/apache_couchdb_160_released/
>
> http://www.reddit.com/r/Database/comments/27svqw/apache_couchdb_160_released/
>
> http://www.reddit.com/r/nosql/comments/27svrx/apache_couchdb_160_released/
>
> http://www.reddit.com/r/CouchDB/comments/27svsk/apache_couchdb_160_released/
>
> Please take a moment to share these links with your friends.
>
> Retweet us if you use Twitter, and upvote us if you use Hacker News, or
> Reddit.
>
> (Note that Hacker News users may want to navigate to the item from the
> front page. I believe up votes are not counted when you link to an
> item directly.)
>
> If you are active on Google+, Lobste.rs, or other relevant social
> media, please share the news there and report back on this thread.
>
> If you like, you could monitor these threads and respond to people
> with questions. This is a great opportunity for community outreach.
>
> If you have any other promotion you'd like to highlight, please reply
> to this thread.
>
> Thanks,
>
> Dirkjan
>
>
>
> --
> Andy Wenk
> Hamburg - Germany
> RockIt!
>
> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
>
> https://people.apache.org/keys/committer/andywenk.asc
>
--
Peter Cooper
Cooper Press
http://cooperpress.com/
Cooper Press Ltd is registered in England #07625723
Registered Office:
30 Lincoln Way
Fairfield Enterprise Centre
Louth, Lincs, UK, LN11 0LS
Fwd: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Andy Wenk <an...@apache.org>.
Hi Peter,
I just want to make sure, you don't miss the great news about the Apache
CouchDB 1.6.0 release :).
All the best
Andy
---------- Forwarded message ----------
From: Dirkjan Ochtman <di...@ochtman.nl>
Date: 10 June 2014 19:32
Subject: [REQUEST] Promote the CouchDB 1.6.0 release
To: "dev@couchdb.apache.org" <de...@couchdb.apache.org>, "
user@couchdb.apache.org" <us...@couchdb.apache.org>,
marketing@couchdb.apache.org
Dear community,
Being a volunteer organisation, we rely on you to help us promote releases.
Here is the official blog post:
https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0
Here is the official tweet:
https://twitter.com/CouchDB/status/476414924412178432
We also have a Hacker News item:
https://news.ycombinator.com/item?id=7873968
And several Reddit items:
http://www.reddit.com/r/programming/comments/27svpz/apache_couchdb_160_released/
http://www.reddit.com/r/Database/comments/27svqw/apache_couchdb_160_released/
http://www.reddit.com/r/nosql/comments/27svrx/apache_couchdb_160_released/
http://www.reddit.com/r/CouchDB/comments/27svsk/apache_couchdb_160_released/
Please take a moment to share these links with your friends.
Retweet us if you use Twitter, and upvote us if you use Hacker News, or
Reddit.
(Note that Hacker News users may want to navigate to the item from the
front page. I believe up votes are not counted when you link to an
item directly.)
If you are active on Google+, Lobste.rs, or other relevant social
media, please share the news there and report back on this thread.
If you like, you could monitor these threads and respond to people
with questions. This is a great opportunity for community outreach.
If you have any other promotion you'd like to highlight, please reply
to this thread.
Thanks,
Dirkjan
--
Andy Wenk
Hamburg - Germany
RockIt!
GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
https://people.apache.org/keys/committer/andywenk.asc
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Noah Slater <ns...@apache.org>.
Thanks so much Dirkjan. Here are the other links:
https://plus.google.com/+CouchDB/posts/fVZ8EJ1aWBE
https://www.facebook.com/permalink.php?story_fbid=544286788936883&id=507603582605204
https://lobste.rs/s/nu8sf5/apache_couchdb_1_6_0_released
Please, please help us to promote. It really helps us get the news
out, which in turn helps us to grow the community, and improve the
project. This is a super easy way to get involved and contribute to
the project. Every bit of help is massively appreciated!
Thank you!
On 10 June 2014 19:32, Dirkjan Ochtman <di...@ochtman.nl> wrote:
> Dear community,
>
> Being a volunteer organisation, we rely on you to help us promote releases.
>
> Here is the official blog post:
>
> https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0
>
> Here is the official tweet:
>
> https://twitter.com/CouchDB/status/476414924412178432
>
> We also have a Hacker News item:
>
> https://news.ycombinator.com/item?id=7873968
>
> And several Reddit items:
>
> http://www.reddit.com/r/programming/comments/27svpz/apache_couchdb_160_released/
> http://www.reddit.com/r/Database/comments/27svqw/apache_couchdb_160_released/
> http://www.reddit.com/r/nosql/comments/27svrx/apache_couchdb_160_released/
> http://www.reddit.com/r/CouchDB/comments/27svsk/apache_couchdb_160_released/
>
> Please take a moment to share these links with your friends.
>
> Retweet us if you use Twitter, and upvote us if you use Hacker News, or Reddit.
>
> (Note that Hacker News users may want to navigate to the item from the
> front page. I believe up votes are not counted when you link to an
> item directly.)
>
> If you are active on Google+, Lobste.rs, or other relevant social
> media, please share the news there and report back on this thread.
>
> If you like, you could monitor these threads and respond to people
> with questions. This is a great opportunity for community outreach.
>
> If you have any other promotion you'd like to highlight, please reply
> to this thread.
>
> Thanks,
>
> Dirkjan
--
Noah Slater
https://twitter.com/nslater
Re: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Rahul Chaudhary <ra...@nosqlweekly.com>.
Thanks for sending it my way. Will check it out.
Sent from my iPhone
> On Jun 10, 2014, at 5:47 PM, Andy Wenk <an...@apache.org> wrote:
>
> Hi Rahul,
>
> I just want to make sure, you don't miss the great news about the Apache CouchDB 1.6.0 release :).
>
> All the best
>
> Andy
>
> ---------- Forwarded message ----------
> From: Dirkjan Ochtman <di...@ochtman.nl>
> Date: 10 June 2014 19:32
> Subject: [REQUEST] Promote the CouchDB 1.6.0 release
> To: "dev@couchdb.apache.org" <de...@couchdb.apache.org>, "user@couchdb.apache.org" <us...@couchdb.apache.org>, marketing@couchdb.apache.org
>
>
> Dear community,
>
> Being a volunteer organisation, we rely on you to help us promote releases.
>
> Here is the official blog post:
>
> https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0
>
> Here is the official tweet:
>
> https://twitter.com/CouchDB/status/476414924412178432
>
> We also have a Hacker News item:
>
> https://news.ycombinator.com/item?id=7873968
>
> And several Reddit items:
>
> http://www.reddit.com/r/programming/comments/27svpz/apache_couchdb_160_released/
> http://www.reddit.com/r/Database/comments/27svqw/apache_couchdb_160_released/
> http://www.reddit.com/r/nosql/comments/27svrx/apache_couchdb_160_released/
> http://www.reddit.com/r/CouchDB/comments/27svsk/apache_couchdb_160_released/
>
> Please take a moment to share these links with your friends.
>
> Retweet us if you use Twitter, and upvote us if you use Hacker News, or Reddit.
>
> (Note that Hacker News users may want to navigate to the item from the
> front page. I believe up votes are not counted when you link to an
> item directly.)
>
> If you are active on Google+, Lobste.rs, or other relevant social
> media, please share the news there and report back on this thread.
>
> If you like, you could monitor these threads and respond to people
> with questions. This is a great opportunity for community outreach.
>
> If you have any other promotion you'd like to highlight, please reply
> to this thread.
>
> Thanks,
>
> Dirkjan
>
> --
> Andy Wenk
> Hamburg - Germany
> RockIt!
>
> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
>
> https://people.apache.org/keys/committer/andywenk.asc
Fwd: [REQUEST] Promote the CouchDB 1.6.0 release
Posted by Andy Wenk <an...@apache.org>.
Hi Rahul,
I just want to make sure, you don't miss the great news about the Apache
CouchDB 1.6.0 release :).
All the best
Andy
---------- Forwarded message ----------
From: Dirkjan Ochtman <di...@ochtman.nl>
Date: 10 June 2014 19:32
Subject: [REQUEST] Promote the CouchDB 1.6.0 release
To: "dev@couchdb.apache.org" <de...@couchdb.apache.org>, "
user@couchdb.apache.org" <us...@couchdb.apache.org>,
marketing@couchdb.apache.org
Dear community,
Being a volunteer organisation, we rely on you to help us promote releases.
Here is the official blog post:
https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0
Here is the official tweet:
https://twitter.com/CouchDB/status/476414924412178432
We also have a Hacker News item:
https://news.ycombinator.com/item?id=7873968
And several Reddit items:
http://www.reddit.com/r/programming/comments/27svpz/apache_couchdb_160_released/
http://www.reddit.com/r/Database/comments/27svqw/apache_couchdb_160_released/
http://www.reddit.com/r/nosql/comments/27svrx/apache_couchdb_160_released/
http://www.reddit.com/r/CouchDB/comments/27svsk/apache_couchdb_160_released/
Please take a moment to share these links with your friends.
Retweet us if you use Twitter, and upvote us if you use Hacker News, or
Reddit.
(Note that Hacker News users may want to navigate to the item from the
front page. I believe up votes are not counted when you link to an
item directly.)
If you are active on Google+, Lobste.rs, or other relevant social
media, please share the news there and report back on this thread.
If you like, you could monitor these threads and respond to people
with questions. This is a great opportunity for community outreach.
If you have any other promotion you'd like to highlight, please reply
to this thread.
Thanks,
Dirkjan
--
Andy Wenk
Hamburg - Germany
RockIt!
GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
https://people.apache.org/keys/committer/andywenk.asc