On 2019-10-02 15:10, Denitsa Burroughs wrote:
> Hi Joan, Adam, et al,
>
> Ilya and I got together to review the deprecations list to a) determine if
> there were any additional breaking changes required for 3.0 and b) ensure
> we had a comprehensive list for documentation and release notes purp
Hi Joan, Adam, et al,
Ilya and I got together to review the deprecations list to a) determine if
there were any additional breaking changes required for 3.0 and b) ensure
we had a comprehensive list for documentation and release notes purposes.
We used this email thread and the tickets Adam create
I added https://github.com/apache/couchdb/issues/2191 to the 3.0 release tasks
but I don’t know exactly what the desired end state looks like there.
Adam
> On Sep 14, 2019, at 3:11 PM, Joan Touzet wrote:
>
> Hi Deni, I think you mean Joan, not Jan. :D
>
> As I mentioned there isn't an issue y
Hi Deni, I think you mean Joan, not Jan. :D
As I mentioned there isn't an issue yet, so we need to create one. I'm
away from my credentials until Tuesday and can address this then, if no
one gets to it first.
-Joan
On 2019-09-11 2:43 p.m., Denitsa Burroughs wrote:
Hi Jan -
Do you happen to
Hi Jan -
Do you happen to have the ticket/link for this?
> I remembered one last deprecation we wanted in 3.0: security tightening,
> which included the deprecation of admin party.
>
Thanks!
Deni
On Mon, Sep 9, 2019 at 2:14 PM Joan Touzet wrote:
> I remembered one last deprecation we wanted i
I remembered one last deprecation we wanted in 3.0: security tightening,
which included the deprecation of admin party.
Jan can you find the ticket on this? I don't think it's the full #1504.
Just new defaults, and we'll need to think thru what happens when
starting up a node that has no [admi
One thing that I reminded myself on is:
> # Proposed deprecations for 3.0, not rebuilt/removed in 4.0
>
> **Feature/Endpoint** |**Replaced by** | **Links**
> --|--|---
> `/{db}/{ddoc}/_show/*`| App server/rev proxy
; for 3.0 (for example documenting the per-access control stuff) or any of
>> the other functionality. In addition if you feel there's something someone
>> with some beginner erlang skill and little familiarity of the project could
>> tackle with minimal guidance I'd b
Tsk, we contributed all of that code without any corresponding documentation?
Thanks for pointing that out Will, I’ve added it to the list.
Adam
> On Sep 5, 2019, at 5:10 AM, Will Holley wrote:
>
> From an operational pov, the compaction daemon was removed in favour of
> smoosh [1]. We owe som
on if you feel there's something someone
>> with some beginner erlang skill and little familiarity of the project could
>> tackle with minimal guidance I'd be happy to help there too!
>>>
>>>
>>> Tabeth
>>>
>>> __
>From an operational pov, the compaction daemon was removed in favour of
smoosh [1]. We owe some documentation around these new subsystems (smoosh,
ioq, ken) and some guides covering common cases (only compact during quiet
periods, disable compaction, etc) to aid migration.
[1] https://github.com/
I found a couple of other bits while grep’ing through the documentation for
“deprecated”:
> * The ``stale`` parameter for views and ``_find`` has been deprecated in
> favour
> of two new parameters: ``stable`` and ``update``. The old ``stale=ok``
> behaviour is equivalent to ``stable=true&up
On 2019-09-04 20:53, Adam Kocoloski wrote:
> Great list, Joan, thanks. I created a handful of GitHub issues for the first
> two sections and tossed them in the “Proposed for 3.x” column. I also
> submitted a PR to address one of them :)
Cheers! I've also retitled that column "3.0 Release Task
Great list, Joan, thanks. I created a handful of GitHub issues for the first
two sections and tossed them in the “Proposed for 3.x” column. I also submitted
a PR to address one of them :)
Out of that list of already-deprecated functionality the only one that gives me
pause is the delayed_commit
Much appreciated, Joan
You're a hero
Johs
> On 4 Sep 2019, at 23:37, Joan Touzet wrote:
>
> Hey Adam,
>
>> When it comes to deprecating and/or removing functionality, I feel like I
>> don’t know exactly where we stand today. We have occasionally described some
>> of the CouchApp functionality
Hey Adam,
> When it comes to deprecating and/or removing functionality, I feel like I
> don’t know exactly where we stand today. We have occasionally described some
> of the CouchApp functionality as already being deprecated, but I’m having
> trouble finding any official record of that in our d
access control stuff) or any of
>> the other functionality. In addition if you feel there's something someone
>> with some beginner erlang skill and little familiarity of the project could
>> tackle with minimal guidance I'd be happy to help there too!
>>>
>
? What this
> would mean in practice is that at some cadence, e.g. 4 times a year
> everything done at that point would be wrapped up in a new version. I think
> this would help the community in that there's a steady march towards
> functionality being available for production use. This
_
From: Jan Lehnardt
Sent: Wednesday, August 7, 2019 12:39:01 PM
To: CouchDB Developers
Subject: Re: Getting started on CouchDB 3.0, and an introduction
Hi Tabeth,
Are you interested in helping out with any of these things?
This thread is meant more as a “who’s prepared to p
Hey Deni,
Warmly welcome!
Peng Hui
From: Denitsa Burroughs
To: dev@couchdb.apache.org
Date: 2019/08/08 02:03 AM
Subject:[EXTERNAL] Re: Getting started on CouchDB 3.0, and an
introduction
Hi all -
Looking forward to working with all of you! As Joan mentioned, my
> with some beginner erlang skill and little familiarity of the project could
> tackle with minimal guidance I'd be happy to help there too!
>
>
> Tabeth
>
> ____
> From: Jan Lehnardt
> Sent: Wednesday, August 7, 2019 12:39:01 PM
> To
e beginner erlang skill
and little familiarity of the project could tackle with minimal guidance I'd be
happy to help there too!
Tabeth
From: Jan Lehnardt
Sent: Wednesday, August 7, 2019 12:39:01 PM
To: CouchDB Developers
Subject: Re: Getting started
ionality
>> being available for production use. This would also tighten the feedback
>> loop between releases and feedback.
>>
>>
>>
>> From: Joan Touzet
>> Sent: Wednesday, August 7, 2019 11:52:01 AM
>> To: Couch
Welcome Deni! :)
* * *
Joan, thanks for writing this up. I’ll def work on #1524 and would like to get
at least a basic variant into 3.0.
Best
Jan
—
> On 7. Aug 2019, at 17:52, Joan Touzet wrote:
>
> Hi everyone,
>
>
>
> Now that we have a path forward for FoundationDB, we also need to get
there's a steady march towards functionality being
> available for production use. This would also tighten the feedback loop
> between releases and feedback.
>
>
> ________________
> From: Joan Touzet
> Sent: Wednesday, August 7, 2019 11:52:01 AM
>
: Wednesday, August 7, 2019 11:52:01 AM
To: CouchDB Developers
Subject: Getting started on CouchDB 3.0, and an introduction
Hi everyone,
Now that we have a path forward for FoundationDB, we also need to get
moving on our best-and-greatest CouchDB-as-is release, namely the 3.x
branch.
If we were
Hi everyone,
Now that we have a path forward for FoundationDB, we also need to get
moving on our best-and-greatest CouchDB-as-is release, namely the 3.x
branch.
If we were to cut CouchDB 3.0 from master today, we'd already have a lot
of great new things since 2.3.1:
* Partitioned DBs
* Open
27 matches
Mail list logo
