if any other help
>>> needed.
>>>
>>> Rgds,
>>>
>>> Mike
>>>
>>>
>>>>
>>>> - Original message -
>>>> From: Felix Haverkamp
>>>> To: CouchDB Developers
>>>> C
if there is a better place to put it or if any other help
>> needed.
>>
>> Rgds,
>>
>> Mike
>>
>>
>>>
>>> - Original message -
>>> From: Felix Haverkamp
>>> To: CouchDB Developers
>>> Cc: Jan L
- Original message -
>> From: Felix Haverkamp
>> To: CouchDB Developers
>> Cc: Jan Lehnardt
>> Subject: [EXTERNAL] Re: 3.0 Release Blog Post Series
>> Date: Tue, Jan 14, 2020 6:19 AM
>>
>> Hey everyone,
>>
>> Hope you are all good. Just wanted
essage -
> From: Felix Haverkamp
> To: CouchDB Developers
> Cc: Jan Lehnardt
> Subject: [EXTERNAL] Re: 3.0 Release Blog Post Series
> Date: Tue, Jan 14, 2020 6:19 AM
>
> Hey everyone,
>
> Hope you are all good. Just wanted to follow up on the blog posts. We hav
Hey everyone,
Hope you are all good. Just wanted to follow up on the blog posts. We have two
drafts (google link below) and Joshua Mintz and Mike Breslin signed up for
Partition queries. It would be great to have more volunteers writing a post:)
Here is a list of what we have so far:
1.
Heya,
I’ve got two drafts up. Feel free to send comments here or directly in the
Google docs.
> On 27. Nov 2019, at 17:35, Jan Lehnardt wrote:
>
> Hey all,
>
> with 3.0 on the horizon, we should start planning some of our
> release communications.
>
> For 2.0, we prepared a set of blog
Partition queries should be included. Sign Mike Breslin and I up to write
it!
Thanks.
-Josh
On Wed, Nov 27, 2019 at 12:16 PM Felix Haverkamp
wrote:
> Hi Everybody,
>
> Thank you Jan!
> I am very exited to be part of it and looking forward to help!
>
> Best
> Felix
>
>
> > On 27. Nov 2019, at
Hi Everybody,
Thank you Jan!
I am very exited to be part of it and looking forward to help!
Best
Felix
> On 27. Nov 2019, at 17:35, Jan Lehnardt wrote:
>
> Hey all,
>
> with 3.0 on the horizon, we should start planning some of our
> release communications.
>
> For 2.0, we prepared a set
Hey all,
with 3.0 on the horizon, we should start planning some of our
release communications.
For 2.0, we prepared a set of blog posts[1], one a week, in the
running up to the 2.0 release, each explaining a certain
feature in more detail. I’d like to suggest that we repeat
that experience,