Hi Deni,

Thanks for the update.

FYI I have completed my review of the work on 1875, and have put significant effort in on the revised CI workflow as requested.

Unfortunately, given the status of where things are, especially with admin change requirements, the one key change for _access that *must* land in 3.0 (and Jan's proposed 2.4 release), and my absence from now until the end of the year for CouchDB, I am -1 on an RC before first week January 2020 but +1 on freezing master for bug fixes and final release steps (bumping fauxton/docs, writing release notes, etc.) only at any point.

Practically speaking we just have this week left for everyone else anyway, and cutting an RC just to meet an arbitrary deadline doesn't make sense to me. That's not how CouchDB has worked in the past, and I am unconvinced it's reasonable for this release.

-Joan


On 2019-12-11 2:05 p.m., Denitsa Burroughs wrote:
Hi all,

Below is the latest status. Given that there are still pending code
changes, we are unable to code freeze at the moment but hope to do so
within the next week. Please review the list below and provide assistance
where possible. After code freeze, only bug fixes will be allowed.

*In progress:*
- 1875 Update SpiderMonkey version
<https://github.com/apache/couchdb/issues/1875> *(Peng Hui)* *- awaiting
final review(s) *
- 2171 Document new management subsystems (smoosh, ioq, ken)
<https://github.com/apache/couchdb/issues/2171>-ioq left. *(Adam) **- ioq
only, doc ticket, not a blocker*
- 1524 Per-document access control  #1524
<https://github.com/apache/couchdb/issues/1524> *(Jan)*
* ~ Dec 13th, partially deferrable to 3.1*
- 2249 Cluster setup does not create IOQ stats database
<https://github.com/apache/couchdb/issues/2249>  *(Adam) *
*- need new ETA*


*- 2191 Tighten up security model
<https://github.com/apache/couchdb/issues/2191> - (Bob) - Bob has a PR for
the Admin_only change, however, there's a pending question in the ticket.
Feedback would be appreciated. Ticket needs to be moved to the In Progress
column on the board.*
*Backlog:*
- Release Notes
- Blog posts (see Jan's email)

Thanks!

Deni

Reply via email to