Hi everyone,

2.3.0 has been languishing for a while. All of the devs seem to be busy in 
their own feature branches, while we have a "tragedy of the commons" with these 
naggling bugs. Please help!

These PRs are at risk of dying if they don't get some +1s soon:

https://github.com/apache/couchdb/pull/1182 - fixed race is_idle
https://github.com/apache/couchdb/pull/1195 - Add support for bulk get with 
Accept:"multipart/mixed" or "multipart/related"

These PRs need just a little more work to be completed:

Blocking 2.3.0:
https://github.com/apache/couchdb/pull/1602 - Remove runtime configurability of 
core system components

Remainder of open PRs:
https://github.com/apache/couchdb/pull/1253 - Validate new document writes 
against max_http_request_size
https://github.com/apache/couchdb/pull/1272 - Record and expose last compaction 
time
https://github.com/apache/couchdb/pull/1337 - Enable discovery of cluster nodes 
through DNS SRV
https://github.com/apache/couchdb/pull/1443 - Add clustered db info
https://github.com/apache/couchdb/pull/1470 - Fix calculation of external size 
for attachments
https://github.com/apache/couchdb/pull/1619 - Implement replicator forced 
session refresh
https://github.com/apache/couchdb/pull/1629 - handle db deletion in load 
validation funs
https://github.com/apache/couchdb/pull/1639 - Switch to python 3 (has a 
companion PR in couchdb-ci)
https://github.com/apache/couchdb/pull/1642 - Set io_priority for couch_index 
pids

These issues are currently slated to be resolved in 2.3.0 and have not seen any 
attention. Please help:

https://github.com/apache/couchdb/issues/1579 - Autocompaction never triggered 
in 2.2.0 (regression from 2.1.0)
https://github.com/apache/couchdb/issues/1600 - Sporadic errors on /_all_docs 
with Cookie auth and system databases
https://github.com/apache/couchdb/issues/1603 - Bad total_rows for 
/{db}/_design_docs
https://github.com/apache/couchdb/issues/1607 - Replicator fails to 
authenticate to open db after cookie timeout (relates to PR #1619)

The other 2 issues in 2.3.0 are close to resolution.

We're very close - just need some more hands on deck.

-Joan

Reply via email to